| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | tharakan(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Subject: | Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 |
| Date: | 2025-04-10 12:28:01 |
| Message-ID: | ed14891b-d2ec-471a-a91f-2ea258c31795@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| 0001-Be-more-conventional-estimating-hash-join-bucket-siz.patch | text/x-patch | 5.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kieran McCusker | 2025-04-10 12:34:36 | Re: Help Please! |
| Previous Message | Daniel Gustafsson | 2025-04-10 11:30:40 | Re: Help Please! |