Re: pg_stat_statements and "IN" conditions - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: pg_stat_statements and "IN" conditions
Date
Msg-id 202502111214.fcfodex6t3sy@alvherre.pgsql
Whole thread Raw
In response to pg_stat_statements and "IN" conditions  (Dmitry Dolgov <9erthalion6@gmail.com>)
Responses Re: pg_stat_statements and "IN" conditions
List pgsql-hackers
Hello

I noticed something that surprised me at first, but on further looking
it should have been obvious: setting pg_stat_statements.query_id_const_merge
affects the query ID for all readers of it, not just pg_stat_statement.
This is good because it preserves the property that pg_stat_activity
entries can be matched to pg_stat_statement entries by query_id.

Looking to commit 0001 soon.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"On the other flipper, one wrong move and we're Fatal Exceptions"
(T.U.X.: Term Unit X  - http://www.thelinuxreview.com/TUX/)



pgsql-hackers by date:

Previous
From: Shlok Kyal
Date:
Subject: Re: Restrict publishing of partitioned table with a foreign table as partition
Next
From: Ilia Evdokimov
Date:
Subject: Re: Move wal_buffers_full to WalUsage (and report it in pgss/explain)