Re: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>

To: buschmann@nidsa.net, pgsql-bugs@lists.postgresql.org

Date: 2023-10-05T15:12:47Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Prevent duplicate RTEPermissionInfo for plain-inheritance parents
- 01575ad788e3 17.0 landed
- 178ee1d858d8 16.1 landed
Fix problems when a plain-inheritance parent table is excluded.
- b1444a09dcb5 16.1 landed
- 8f4a6b9e4f5b 14.10 landed
- 1268e7378123 15.5 landed
- 387f9ed0a083 17.0 landed
Doc: indexUnchanged is strictly a hint.
- 74e5ea1e002f 17.0 landed
- cf89d3052d62 16.1 landed
- be2502947f29 15.5 landed
- df73ca35144a 14.10 landed

On Thu, Oct 5, 2023 at 8:05 AM PG Bug reporting form <noreply@postgresql.org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference:      18147
> Logged by:          Hans Buschmann
> Email address:      buschmann@nidsa.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.