Re: Replace IN VALUES with ANY in WHERE clauses during optimization
Alena Rybakina <a.rybakina@postgrespro.ru>
From: Alena Rybakina <a.rybakina@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Geoghegan <pg@bowt.ie>, Andres Freund <andres@anarazel.de>,
Alexander Korotkov <aekorotkov@gmail.com>,
Andrei Lepikhov <lepihov@gmail.com>, Ivan Kush <ivan.kush@tantorlabs.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>,
Laurenz Albe <laurenz.albe@cybertec.at>
Date: 2025-04-04T16:30:47Z
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
On 04.04.2025 19:00, Tom Lane wrote: > Peter Geoghegan<pg@bowt.ie> writes: >> Is somebody going to commit this soon? Alexander? > Done. > > I thought the point of the test case was to check VALUES folding > on both sides of the join. I'm not sure why that's actually > a useful expenditure of test cycles, but Alena's patch undid that > without adjusting the comment claiming that's what it's doing. > So I kept the shape of the test the same while substituting > hopefully-stabler tables as she did. Yes, that's right. Thank you. > If it's still not stable I think the next step is to nuke both > test queries, since I remain of the opinion that they're likely > a waste of cycles. > > Agree. -- Regards, Alena Rybakina Postgres Professional