Re: pg_stat_statements and "IN" conditions

Yasuo Honda <yasuo.honda@gmail.com>

From: Yasuo Honda <yasuo.honda@gmail.com>

To: Maciek Sakrejda <m.sakrejda@gmail.com>

Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>, pgsql-hackers@lists.postgresql.org, Dmitry Dolgov <9erthalion6@gmail.com>

Date: 2023-10-09T01:46:43Z

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

Hi, this is my first email to the pgsql hackers.

I came across this email thread while looking at
https://github.com/rails/rails/pull/49388 for Ruby on Rails one of the
popular web application framework by replacing every query `in` clause
with `any` to reduce similar entries in `pg_stat_statements`.

I want this to be solved on the PostgreSQL side, mainly because I want
to avoid replacing
every in clause with any to reduce similar entries in pg_stat_statements.

It would be nice to have this patch reviewed.

As I'm not familiar with C and PostgreSQL source code, I'm not
reviewing this patch myself,
I applied this patch to my local PostgreSQL and the Active Record unit
tests ran successfully.
--
Yasuo Honda