Re: pg17: XX000: no relation entry for relid 0
Tender Wang <tndrwang@gmail.com>
From: Tender Wang <tndrwang@gmail.com>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@lists.postgresql.org, Paul Jungwirth <pj@illuminatedcomputing.com>, Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>
Date: 2026-04-11T01:31:59Z
Lists: pgsql-hackers
Attachments
- 0001-Fix-no-relation-entry-for-relid-0-in-nested-UNION-AL.patch (application/octet-stream) patch 0001
Richard Guo <guofenglinux@gmail.com> 于2026年4月10日周五 22:39写道:
>
> On Fri, Apr 10, 2026 at 9:49 PM Tender Wang <tndrwang@gmail.com> wrote:
> > Justin Pryzby <pryzby@telsasoft.com> 于2026年4月10日周五 18:54写道:
> > > CREATE VIEW x AS SELECT NULL::int[]
> > > UNION ALL SELECT NULL::int[]
> > > UNION ALL SELECT ARRAY[NULL::bigint];
> > >
> > > SELECT FROM x;
> > > ERROR: XX000: no relation entry for relid 0
>
> Nice catch. It seems that we need at least three branches to
> reproduce this, so that there's a nested UNION ALL whose output type
> doesn't match the parent's expected type. At the outer branch maybe
> we can use NULL::bigint[] instead to be a little simpler.
>
> SELECT NULL::int[] UNION ALL SELECT NULL::int[] UNION ALL SELECT NULL::bigint[];
> ERROR: no relation entry for relid 0
Yes, add it to the test case.
>
> > I didn't think too much at now, a quick fix as below:
> > diff --git a/src/backend/utils/adt/selfuncs.c b/src/backend/utils/adt/selfuncs.c
> > index 4160d2d6e24..ff93fc3ac8a 100644
> > --- a/src/backend/utils/adt/selfuncs.c
> > +++ b/src/backend/utils/adt/selfuncs.c
> > @@ -2265,6 +2265,9 @@ estimate_array_length(PlannerInfo *root, Node *arrayexpr)
> > AttStatsSlot sslot;
> > double nelem = 0;
> >
> > + if (IsA(arrayexpr, Var) && ((Var *) arrayexpr)->varno == 0)
> > + return 10;
> > +
> > examine_variable(root, arrayexpr, 0, &vardata);
> > if (HeapTupleIsValid(vardata.statsTuple))
> > {
> >
> > Any thoughts?
>
> This looks like the right fix to me. We can use some comment here.
comments added.
Please see the attached patch.
--
Thanks,
Tender Wang
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix estimate_array_length error with set-operation array coercions
- 93ed18720105 17.10 landed
- 13e20d1c9d99 18.4 landed
- 77d0e82e5885 19 (unreleased) landed