Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements

Alexander Korotkov <aekorotkov@gmail.com>

From: Alexander Korotkov <aekorotkov@gmail.com>

To: Andrei Zubkov <zubkov@moonset.ru>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2023-11-25T00:45:07Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Improve quoting in some error messages
- 07e5e6674233 14.0 cited

Attachments

0002-Track-statement-entry-timestamp-in-contrib-pg_st-v27.patch (application/octet-stream) patch v27-0002
0001-Add-NOT-NULL-checking-of-pg_stat_statements_rese-v27.patch (application/octet-stream) patch v27-0001

Hi!

On Fri, Nov 17, 2023 at 10:40 AM Andrei Zubkov <zubkov@moonset.ru> wrote:
>
> A little fix in "level_tracking" tests after merge.

I've reviewed this patch. I think this is the feature of high demand.
New columns (stats_since and minmax_stats_since) to the
pg_stat_statements view, enhancing the granularity and precision of
performance monitoring. This addition allows database administrators
to have a clearer understanding of the time intervals for statistics
collection on each statement. Such detailed tracking is invaluable for
performance tuning and identifying bottlenecks in database operations.

I think the design was well-discussed in this thread.  Implementation
also looks good to me.  I've just slightly revised the commit
messages.

I'd going to push this patchset if no objections.

------
Regards,
Alexander Korotkov