From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Andrei Zubkov <zubkov(at)moonset(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements |
Date: | 2023-11-25 00:45:07 |
Message-ID: | CAPpHfds36dkLWCcXuVaOnCMGRRULnQu5Tc5ninz-5EX8VDvMVw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi!
On Fri, Nov 17, 2023 at 10:40 AM Andrei Zubkov <zubkov(at)moonset(dot)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
Attachment | Content-Type | Size |
---|---|---|
0002-Track-statement-entry-timestamp-in-contrib-pg_st-v27.patch | application/octet-stream | 38.6 KB |
0001-Add-NOT-NULL-checking-of-pg_stat_statements_rese-v27.patch | application/octet-stream | 56.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2023-11-25 01:13:47 | Re: POC, WIP: OR-clause support for indexes |
Previous Message | Bruce Momjian | 2023-11-25 00:44:25 | Re: pg_walfile_name_offset can return inconsistent values |