| 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 09:22:03 |
| Message-ID: | 1953aec168224b95b0c962a622bef0794da6ff40.camel@moonset.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi, Kuroda!
I've intended to change the pg_stat_statements version with rebasing
this patch to the current master branch state. Now this is commit
07e5e66.
But I'm unable to test the patch - it seems that pg_stat_statements is
receiving queryId = 0 for every statements in every hook now and
statements are not tracked at all.
Am I mistaken somewhere? Maybe you know why this is happening?
Thank you!
--
Andrei Zubkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On Fri, 2021-04-09 at 00:23 +0000, kuroda(dot)hayato(at)fujitsu(dot)com wrote:
> Dear Andrei,
>
> > I think, yes, version of pg_stat_statements is need to be updated.
> > Is
> > it will be 1.10 in PG15?
>
> 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
>
>
> Best Regards,
> Hayato Kuroda
> FUJITSU LIMITED
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2021-04-14 09:32:14 | Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements |
| Previous Message | Pavel Stehule | 2021-04-14 09:12:21 | Re: jsonb subscripting assignment performance |