From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hans Buschmann <buschmann@nidsa.net>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
Date: Sun, 08 Oct 2023 11:24:38 -0400
Message-ID: <3319880.1696778678@sss.pgh.pa.us> (raw)
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>
Hans Buschmann <buschmann@nidsa.net> writes:
> For your reference I include a simple dump of a test case database, which 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, buschmann@nidsa.net, david.g.johnston@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
In-Reply-To: <3319880.1696778678@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox