Re: BUG #18170: Unexpected error: no relation entry for relid 3

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: zuming(dot)jiang(at)inf(dot)ethz(dot)ch, pgsql-bugs(at)lists(dot)postgresql(dot)org, Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Subject: Re: BUG #18170: Unexpected error: no relation entry for relid 3
Date: 2023-10-26 15:21:07
Message-ID: 4ecab120-6be3-4cf6-a2a0-249c73ae91d4@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)jiang(at)inf(dot)ethz(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2023-10-26 15:33:10 Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict
Previous Message PG Bug reporting form 2023-10-26 15:11:39 BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict