Re: pg17: XX000: no relation entry for relid 0

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Tender Wang <tndrwang@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@lists.postgresql.org, Paul Jungwirth <pj@illuminatedcomputing.com>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2026-04-10T20:34:34Z
Lists: pgsql-hackers
On Fri, Apr 10, 2026 at 11:38:50PM +0900, Richard Guo wrote:
> 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.

Indeed, three branches:
$ git branch --contains 9391f7152
+ REL_17_STABLE
+ REL_18_STABLE
* master
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix estimate_array_length error with set-operation array coercions