From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Problems around compute_query_id |
Date: | 2021-04-12 06:12:40 |
Message-ID: | YHPkU8hFi4no4NSw@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
Starting a new thread as the one that has introduced compute_query_id
is already long enough.
Fujii-san has reported on Twitter that enabling the computation of
query IDs does not work properly with log_statement as the query ID is
calculated at parse analyze time and the query is logged before that.
As far as I can see, that's really a problem as any queries logged are
combined with a query ID of 0, and log parsers would not really be
able to use that, even if the information provided by for example
log_duration gives the computed query ID prevent in pg_stat_activity.
While making the feature run on some test server, I have noticed that
%Q would log some garbage query ID for autovacuum workers that's kept
around. That looks wrong.
Thoughts?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2021-04-12 06:20:41 | Re: Performance degradation of REFRESH MATERIALIZED VIEW |
Previous Message | Tom Lane | 2021-04-12 06:04:13 | Re: Uninitialized scalar variable (UNINIT) (src/backend/statistics/extended_stats.c) |