Re: Apply the "LIMIT 1" optimization to partial DISTINCT
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Richard Guo <guofenglinux@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-01-31T04:25:48Z
Lists: pgsql-hackers
On Fri, 26 Jan 2024 at 21:14, David Rowley <dgrowleyml@gmail.com> wrote: > However, having said that. Parallel plans are often picked when there > is some highly selective qual as parallel_tuple_cost has to be applied > to fewer tuples for such plans, so probably this is worth doing. I was messing around with your test case and didn't manage to get any plan that had any rows to use the partial path with the LIMIT. I ended up dropping the test that was checking the results were empty as I didn't think it added much more value over the EXPLAIN output. I pushed the result. Thanks for working on this. David
Commits
-
Consider the "LIMIT 1" optimization with parallel DISTINCT
- b588cad68882 17.0 landed