| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Richard Guo <guofenglinux(at)gmail(dot)com> |
| Subject: | Re: JumbleQuery ma treat different GROUP BY expr as the same |
| Date: | 2026-01-11 16:19:30 |
| Message-ID: | 3354376.1768148370@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Sat, Jan 10, 2026 at 11:46:27AM -0500, Tom Lane wrote:
>> So I'm inclined to think this was an unintentional change of behavior.
> The difference of behavior is between v17 and v18, as an effect of
> 247dea89f761. I know that we should not break query ID computations
> in stable branches, but v18 is very recent and we still have many
> years to support it.. So I would like to suggest that we make an
> exception and backpatch a fix to v18. This behavior is not cool for
> users.
I agree we should fix it in v18, but we really need to push to have
the fix in 18.2 rather than delay longer. (IME, the .2 release is
about when our more risk-averse users start to think about upgrading.)
So there's a time limit on getting this done.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-01-11 16:43:41 | Re: GIN pageinspect support for entry tree and posting tree |
| Previous Message | Xuneng Zhou | 2026-01-11 12:56:57 | Re: Add WALRCV_CONNECTING state to walreceiver |