Re: pg_stat_statements and "IN" conditions

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>

To: Sergei Kornilov <sk@zsrv.org>, Dmitry Dolgov <9erthalion6@gmail.com>

Cc: Michael Paquier <michael@paquier.xyz>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Marcos Pegoraro <marcos@f10.com.br>, vignesh C <vignesh21@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Zhihong Yu <zyu@yugabyte.com>, David Steele <david@pgmasters.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Greg Stark <stark@mit.edu>, Pavel Trukhanov <pavel.trukhanov@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>

Date: 2023-02-09T13:30:34Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Introduce squashing of constant lists in query jumbling
- 62d712ecfd94 18.0 landed
Make documentation builds reproducible
- b0f0a9432d0b 17.0 cited
Include values of A_Const nodes in query jumbling
- 9ba37b2cb6a1 16.0 cited
Teach planner about more monotonic window functions
- 456fa635a909 16.0 cited
Split up guc.c for better build speed and ease of maintenance.
- 0a20ff54f5e6 16.0 cited

On 07.02.23 21:14, Sergei Kornilov wrote:
> It seems a little strange to me that with const_merge_threshold = 1, such a test case gives the same result as with const_merge_threshold = 2

What is the point of making this a numeric setting?  Either you want to 
merge all values or you don't want to merge any values.