PG15 beta1 fix pg_stat_statements view document
Hi hackers,
The attached patch modifies the pg_stat_statements view documentation updated in PostgreSQL 15 Beta 1.
The data type of the following columns in the pg_stat_statements view is bigint in the current document,
but it is actually double precision.
jit_generation_time
jit_inlining_time
jit_optimization_time
jit_emission_time
Regards,
Noriyoshi Shinoda
Attachments:
pg_stat_statements_doc_v1.diffapplication/octet-stream; name=pg_stat_statements_doc_v1.diffDownload+4-4
On Fri, May 20, 2022 at 12:46:03PM +0000, Shinoda, Noriyoshi (PN Japan FSIP) wrote:
The attached patch modifies the pg_stat_statements view documentation updated in PostgreSQL 15 Beta 1.
The data type of the following columns in the pg_stat_statements view is bigint in the current document,
but it is actually double precision.
jit_generation_time
jit_inlining_time
jit_optimization_time
jit_emission_time
I think there is a typo in the change to the jit_optimization_time section,
but otherwise it looks good to me.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
On Fri, May 20, 2022 at 04:04:29PM -0700, Nathan Bossart wrote:
I think there is a typo in the change to the jit_optimization_time section,
but otherwise it looks good to me.
Yes, as of "double precisiodouble precision". All these four fields
are indeed doubles in the code, for what looks like a copy-pasto from
57d6aea. Will fix.
--
Michael
Hi,
Thank you for your comment.
I attached the fixed patch.
-----Original Message-----
From: Michael Paquier <michael@paquier.xyz>
Sent: Saturday, May 21, 2022 12:33 PM
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi.shinoda@hpe.com>; PostgreSQL-development <pgsql-hackers@postgresql.org>; magnus@hagander.net
Subject: Re: PG15 beta1 fix pg_stat_statements view document
On Fri, May 20, 2022 at 04:04:29PM -0700, Nathan Bossart wrote:
I think there is a typo in the change to the jit_optimization_time
section, but otherwise it looks good to me.
Yes, as of "double precisiodouble precision". All these four fields are indeed doubles in the code, for what looks like a copy-pasto from 57d6aea. Will fix.
--
Michael