Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 - Mailing list pgsql-bugs

From Andrei Lepikhov
Subject Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
Date
Msg-id ed14891b-d2ec-471a-a91f-2ea258c31795@gmail.com
Whole thread Raw
In response to BUG #18885: ERROR: corrupt MVNDistinct entry - 2  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
List pgsql-bugs
On 4/9/25 15:46, PG Bug reporting form wrote:
> The following SQL triggers "ERROR: corrupt MVNDistinct entry", however this
> seems to be unrelated to a recent bugfix[1] for a similar issue (thus '2' in
> the $SUBJECT).
That's my fault.
We wanted to avoid using of the add_unique_group_var, but forgot it does 
some necessary stuff.
Here, I attempt to use this routine in the hash join bucket size 
estimation. I transformed it a little, made it more general. Not sure it 
is the best design, but it is debatable.

-- 
regards, Andrei Lepikhov
Attachment

pgsql-bugs by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Help Please!
Next
From: Kieran McCusker
Date:
Subject: Re: Help Please!