On Wed, Apr 7, 2021 at 08:54:02PM -0400, Bruce Momjian wrote: > > > I am also confused about the inconsistency of calling the GUC > > > compute_query_id (with underscore), but pg_stat_activity.queryid. If we > > > make it pg_stat_activity.query_id, it doesn't match most of the other > > > *id columsns in the table, leader_pid, usesysid, backend_xid. Is that > > > OK?I know I suggested pg_stat_activity.query_id, but maybe I was wrong. > > > > Mmm, most of the columns in pg_stat_activity do have a "_", so using > > query_id > > would make more sense. > > OK, let me work on a patch to change that part.
Uh, it is 'queryid' in pg_stat_statements: https://www.postgresql.org/docs/13/pgstatstatements.html queryid bigint Internal hash code, computed from the statement's parse tree I am not sure if we should have pg_stat_activity use underscore, or the GUC use underscore. The problem is that queryid can easily look like quer-yid. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.