| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 18 GA press release draft |
| Date: | 2025-09-12 02:21:42 |
| Message-ID: | 56a4b3ff-fff3-4b8f-a8e2-b85ffc19b783@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/10/25 3:59 PM, Peter Geoghegan wrote:
> "It can also automatically transform queries with `OR` constructs in
> their `WHERE` clause into a logically equivalent IN() representation
> that can be pushed down to index scan nodes, leading to significantly
> faster execution".
Thanks for the detailed explanation, I'm proposing:
"It can also optimize queries that use `OR` conditions in a `WHERE` to
use an index, leading to significantly faster execution."
since the mechanism of the transformation is less important, but the
outcome is that people can benefit from the previous optimziation
without having to rewrite their queries.
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2025-09-12 02:25:55 | Re: PostgreSQL 18 GA press release draft |
| Previous Message | Richard Guo | 2025-09-12 02:21:15 | Re: Reduce "Var IS [NOT] NULL" quals during constant folding |