| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(at)vondra(dot)me> |
| Cc: | Andrei Lepikhov <lepihov(at)gmail(dot)com>, 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-16 04:11:42 |
| Message-ID: | CAApHDvrk3jYTe2WgB5ZaTKC3JHgVWhK3FD1gy7A3OYmrQH3+RQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 16 Apr 2025 at 01:16, Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> In any case, such rework seems out of scope for PG18 - it's much more
> than a fix for the bug.
This is the reason I stopped short of adjusting the code in the patch
I proposed in [1]. Speaking of which, do you have any views on that?
It seems much more likely that someone would have caught the issue
being reported here when writing the patch or during review if there
was some sort of documentation to mention the function can't handle
duplicate GroupVarInfos.
I'll look at that patch again in the next few days with aims to push
it unless someone has something to say about it.
David
[1] https://postgr.es/m/CAApHDvocZCUhM9W9mJ39d6oQz7ePKoqFnao_347mvC-A7QatcQ@mail.gmail.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2025-04-16 06:57:08 | Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 |
| Previous Message | Thomas Munro | 2025-04-16 00:34:29 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows |