From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hans Buschmann <buschmann@nidsa.net>
cc: "David G. Johnston" <david.g.johnston@gmail.com>,
        "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid
 xxxxx
In-reply-to: <9fdfed847859435e8641e613198be9e3@nidsa.net>
References: <18147-6fc796538913ee88@postgresql.org>
 <CAKFQuwYFq-Q2rxbXXBmdHCAEFm-Pu_qhPAEi-PO+LmjtYN2hhg@mail.gmail.com>,<2796464.1696525626@sss.pgh.pa.us>
 <9fdfed847859435e8641e613198be9e3@nidsa.net>
Comments: In-reply-to Hans Buschmann <buschmann@nidsa.net>
	message dated "Sun, 08 Oct 2023 13:16:52 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3319879.1696778678.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 08 Oct 2023 11:24:38 -0400
Message-ID: <3319880.1696778678@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3319880.1696778678%40sss.pgh.pa.us>
Precedence: bulk

Hans Buschmann <buschmann@nidsa.net> writes:
> For your reference I include a simple dump of a test case database, whic=
h executes the queries but does NOT reproduce the error.
> This case seems much more complicated then I thought on first view.

Hmm.  The most likely explanation for the error sometimes appearing
and sometimes not is that it depends on the shape of the selected
query plan, which in turn would depend on current pg_statistics
contents.

Perhaps you could devise some dummy data that would repro the issue
and you could share with us?

			regards, tom lane