| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, bryfox(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19007: Planner fails to choose partial index with spurious 'not null' |
| Date: | 2025-12-10 02:11:53 |
| Message-ID: | CAMbWs48t5NDKQMo=ROpgAgx6emUjd6r0zscRmm_JzRLSssC-YA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Sep 26, 2025 at 6:20 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> Here is an updated version of the patch. In the commit message, I've
> explained why I think the additional call to eval_const_expressions is
> not a performance concern. I've also added a test case to validate
> that NullTest quals in index expressions can now be reduced.
>
> One concern I have is that this fix can only be applied to master;
> there's no way to backpatch it to v17 or v18. This means that the
> issue won't exist in v16 or earlier, nor in v19 and later, but it will
> persist in v17 and v18. I have no idea what we should do for v17 and
> v18.
I've pushed this fix to master. Still no idea what to do for v17 and
v18.
- Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-12-10 03:46:10 | Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs |
| Previous Message | Richard Guo | 2025-12-10 02:01:49 | Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) |