| From: | Yasuo Honda <yasuo(dot)honda(at)gmail(dot)com> |
|---|---|
| To: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
| Cc: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Subject: | Re: pg_stat_statements and "IN" conditions |
| Date: | 2023-10-09 01:46:43 |
| Message-ID: | CAKmOUTmDJ_p9PrEX5vfnS-fz-n8tdYQ6xcApeVrBt5yPkzxgqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2023-10-09 01:49:59 | Re: Draft LIMIT pushdown to Append and MergeAppend patch |
| Previous Message | David Rowley | 2023-10-09 00:52:40 | Re: Draft LIMIT pushdown to Append and MergeAppend patch |