Re: BUG #18170: Unexpected error: no relation entry for relid 3 - Mailing list pgsql-bugs

From Vik Fearing
Subject Re: BUG #18170: Unexpected error: no relation entry for relid 3
Date
Msg-id 4ecab120-6be3-4cf6-a2a0-249c73ae91d4@postgresfriends.org
Whole thread Raw
In response to BUG #18170: Unexpected error: no relation entry for relid 3  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: BUG #18170: Unexpected error: no relation entry for relid 3  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-bugs
On 10/26/23 16:01, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      18170
> Logged by:          Zuming Jiang
> Email address:      zuming.jiang@inf.ethz.ch
> PostgreSQL version: 16.0

This should be 17devel

> Operating system:   Ubuntu 20.04
> Description:
> 
> My fuzzer finds a bug in Postgres, which triggers an unexpected error.

This bisects to d3d55ce571369dad6e1d582f1655e5a3fbd8594a, Remove useless 
self-joins.
-- 
Vik Fearing




pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict