Re: Replace IN VALUES with ANY in WHERE clauses during optimization

Alexander Korotkov <aekorotkov@gmail.com>

From: Alexander Korotkov <aekorotkov@gmail.com>

To: Alena Rybakina <a.rybakina@postgrespro.ru>

Cc: Andrei Lepikhov <lepihov@gmail.com>, Ivan Kush <ivan.kush@tantorlabs.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, Laurenz Albe <laurenz.albe@cybertec.at>

Date: 2025-04-03T15:26:48Z

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 →

Stabilize regression test from c0962a113.
- 3ba2cdaa4541 18.0 landed
Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate
- c0962a113d1f 18.0 landed
Extract make_SAOP_expr() function from match_orclause_to_indexcol()
- d48d2e2dc8be 18.0 landed

Attachments

v9-0001-Extract-make_SAOP_expr-function-from-match_orclau.patch (application/octet-stream) patch v9-0001
v9-0002-Convert-x-IN-VALUES-.-to-x-ANY-.-then-appropriate.patch (application/octet-stream) patch v9-0002

On Thu, Apr 3, 2025 at 5:18 PM Alena Rybakina <a.rybakina@postgrespro.ru> wrote:
> Okay, I agree with you.

Good.  I've reflected this limitation in comments and the commit
message.  Also, I've adjust regression tests by removing excessive
ones and adding more important cases.  I'm going to push this if no
objections.

------
Regards,
Alexander Korotkov
Supabase