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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>, Richard Guo <guofenglinux(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, 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-29 15:56:56
Message-ID: 2141583.1698595016@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> I made some beautification of the patch by Andrei. I also removed the
> part which changes the target list for estimate_num_groups(). Any
> objections to pushing this?

It seems moderately likely that this will break as much as it fixes.

I've not studied the original patch enough to understand why you need
to be playing strange games with tree mutation rules, but I suspect
that this is band-aiding over some rather fundamentally bad code.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2023-10-30 02:01:02 Re: BUG #18170: Unexpected error: no relation entry for relid 3
Previous Message Tom Lane 2023-10-29 15:53:35 Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly