Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
От | Richard Guo |
---|---|
Тема | Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error |
Дата | |
Msg-id | CAMbWs49P6+7dekSSe5z4thr3AMvuYAJy5GKD5HKzw8x+8oR9hw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
|
Список | pgsql-bugs |
On Wed, Sep 3, 2025 at 10:19 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Richard Guo <guofenglinux@gmail.com> writes: > > One thing I'm not quite sure about is whether we should backpatch this > > fix to pre-v17 branches. Prior to v17, estimate_array_length() wasn't > > taught to use statistics, so this error isn't reproducible there. > > OTOH, passing a root without a valid simple_rel_array to > > cost_qual_eval() still seems potentially unsafe. What do you think? > 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). - Richard
В списке pgsql-bugs по дате отправления: