Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
От | David Rowley |
---|---|
Тема | Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 |
Дата | |
Msg-id | CAApHDvrk3jYTe2WgB5ZaTKC3JHgVWhK3FD1gy7A3OYmrQH3+RQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 (Tomas Vondra <tomas@vondra.me>) |
Ответы |
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
|
Список | pgsql-bugs |
On Wed, 16 Apr 2025 at 01:16, Tomas Vondra <tomas@vondra.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
В списке pgsql-bugs по дате отправления: