Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements

From: Andrei Zubkov <zubkov(at)moonset(dot)ru>
To: "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Seino Yuki <seinoyu(at)oss(dot)nttdata(dot)com>
Subject: Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements
Date: 2021-04-14 14:21:55
Message-ID: 522845e1854a5293354be54544266077f05e16d4.camel@moonset.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, Kuroda!

On Fri, 2021-04-09 at 00:23 +0000, kuroda(dot)hayato(at)fujitsu(dot)com wrote:
> I think you are right.
> According to [1] we can bump up the version per one PG major version,
> and any features are not committed yet for 15.
>
> [1]: https://www.postgresql.org/message-id/20201202040516.GA43757@nol

Version 2 of patch attached. 
pg_stat_statements version is now 1.10 and patch is based on 0f61727.

--
Andrei Zubkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Attachment Content-Type Size
v2-0001-pg_stat_statements-Track-statement-entry-timestamp.patch text/x-patch 11.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-04-14 14:27:11 Re: [PATCH] Identify LWLocks in tracepoints
Previous Message Mead, Scott 2021-04-14 14:17:45 Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay