| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | buschmann(at)nidsa(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx |
| Date: | 2023-10-05 15:12:47 |
| Message-ID: | CAKFQuwYFq-Q2rxbXXBmdHCAEFm-Pu_qhPAEi-PO+LmjtYN2hhg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Oct 5, 2023 at 8:05 AM PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18147
> Logged by: Hans Buschmann
> Email address: buschmann(at)nidsa(dot)net
> PostgreSQL version: 16.0
> Operating system: Fedora 38 x86-64 64bit, also on Win64
> Description:
>
> The query is quite simplified.. Perhaps it is good to now, that the table
> or_followup has an inherited table or_followup_archiv (= relid 17034) which
> is chosen by of_season and has not the same index definitions as
> or_followup.
>
>
The simplified query is preferred so long as it produces the error - but
you really should be providing the create table commands to make the entire
script self-contained.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-10-05 17:07:06 | Re: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx |
| Previous Message | David G. Johnston | 2023-10-05 15:07:55 | Re: BUG #18148: Handle null in a date/time fields when passing empty arrays issue |