Re: Issue in recent pg_stat_statements? - Mailing list pgsql-hackers

From David Christensen
Subject Re: Issue in recent pg_stat_statements?
Date
Msg-id CAOxo6X+Giy8M31b-dEGFMZrPyLPWeAES6+2uB8wijLRFrbJj9Q@mail.gmail.com
Whole thread Raw
In response to Re: Issue in recent pg_stat_statements?  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Issue in recent pg_stat_statements?
List pgsql-hackers
> Is this an expected change, or is this in fact broken?  In previous revisions, this was showing the INSERT and SELECT at the very least.  I'm unclear as to why the regression test is still passing, so want to verify that I'm not doing something wrong in the testing.

Yes, you want to look into the queryid functionality. See
https://www.postgresql.org/message-id/flat/35457b09-36f8-add3-1d07-6034fa585ca8%40oss.nttdata.com

Interface changes may still be coming in 14 for that. Or warnings.

Hmm, I'm unclear as to why you would potentially want to use pg_stat_statements *without* this functionality.  At the very least, it violates POLA — I spent the better part of a day thinking this was a bug due to the expected behavior being so obvious I wouldn't have expected any different.

In any case, this discussion is better had on a different thread.  Thanks at least for explaining what I was seeing.

Best,

David

pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: compute_query_id and pg_stat_statements
Next
From: Bharath Rupireddy
Date:
Subject: Re: Enhanced error message to include hint messages for redundant options error