Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
Date
Msg-id 711590.1756862355@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error  (Richard Guo <guofenglinux@gmail.com>)
Responses Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
List pgsql-bugs
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 ...

            regards, tom lane



pgsql-bugs by date:

Previous
From: Richard Guo
Date:
Subject: Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
Next
From: ocean_li_996
Date:
Subject: Re:BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset