| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error |
| Date: | 2025-09-05 04:00:00 |
| Message-ID: | 53006653-ada7-40aa-9ef8-f52ca0bda4a4@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hello Tom and Richard,
03.09.2025 11:08, Richard Guo wrote:
>> Yeah, "is there any other instance of this problem?" is the $64
>> question here. I was initially thinking v17 is sufficient, but
>> the possibility that some extension might be vulnerable makes
>> me lean to back-patching further. Your call ...
> I've decided to backpatch this fix to pre-v17 branches: using a root
> that lacks a valid simple_rel_array in a cost estimation function
> seems like a pitfall waiting to happen. I've included an explanation
> of this backpatch decision in the commit message and have pushed the
> fix (the test case is not included in pre-v17 branches though).
Thank you for fixing that anomaly!
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 李海洋 (陌痕) | 2025-09-05 05:13:20 | 回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset |
| Previous Message | Hayato Kuroda (Fujitsu) | 2025-09-05 02:28:45 | RE: BUG #19041: Logical replication locks wal processing |