| From: | Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com> |
|---|---|
| To: | Mert Kul <mertkul669(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Richard Guo <guofenglinux(at)gmail(dot)com> |
| Subject: | Re: BUG #19752: GROUP BY on a constant and a cast to a length-limited array type crashes the server while planning |
| Date: | 2026-10-23 04:49:29 |
| Message-ID: | CAB8bMitsxkXu1WBDAnbAX4R5ZsqVZ+MQyUs+YxDiBcJcpbZjfQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
пн, 12 окт. 2026 г., 22:54 Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>:
>
> пн, 12 окт. 2026 г. в 22:48, Mert Kul <mertkul669(at)gmail(dot)com>:
>
>> Thanks for working on this!
>>
>> Is this patch considered the definitive fix for the underlying issue, or
>> is it more of a temporary workaround?
>> In particular, do you think matching grouping expressions by *ressortgroupref
>> *fully addresses the problem,
>> including the potential for incorrect query results, or are further
>> changes needed?
>>
>
> Hi, Mert!
>
> We need Tom to look at my solution, he might not like it :). Although I
> think I took his wishes into account.
>
Hi, Tom!
Could you take a look at the patch and check whether I've chosen the right
direction for the fix?
Thanks in advance for your time.
---
Regards,
Rachitskiy Andrey
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-10-23 05:19:32 | Re: pg_stat_statements stores WITH HOLD cursor query with literals |
| Previous Message | Tender Wang | 2026-10-23 03:42:10 | Re: BUG #19765: Wrong result from a chain of LEFT JOINs since v16 |