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

From Julien Rouhaud
Subject Re: Issue in recent pg_stat_statements?
Date
Msg-id CAOBaU_b7_6KzeVTxn3Mf4oTGHgfVpYkVExsHUjbJE8z_g9oQfg@mail.gmail.com
Whole thread Raw
In response to Re: Issue in recent pg_stat_statements?  (David Christensen <david.christensen@crunchydata.com>)
Responses Re: Issue in recent pg_stat_statements?  (David Christensen <david.christensen@crunchydata.com>)
List pgsql-hackers
On Mon, Apr 26, 2021 at 11:40 PM David Christensen
<david.christensen@crunchydata.com> wrote:
>>
>> > Is this an expected change, or is this in fact broken?  In previous revisions, this was showing the INSERT and
SELECTat the very least.  I'm unclear as to why the regression test is still passing, so want to verify that I'm not
doingsomething 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.

Using pg_stat_statements with a different query_id semantics without
having to fork pg_stat_statements.



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: ERROR: relation "sql_features" does not exist
Next
From: Stephen Frost
Date:
Subject: Re: compute_query_id and pg_stat_statements