Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>, Tender Wang <tndrwang(at)gmail(dot)com>, syzhong16(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
Date: 2026-09-11 01:03:24
Message-ID: CAMbWs4_fV6BjBDaBi8QZ36OrApo-65JMti=2zGqbwUkb0mjdVQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Sep 11, 2026 at 6:54 AM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> I also like idea of usage of enable_sort all the version in this case.
> This would simplify backpatching and reduce divergence between
> versions.

I believe one of the goals of commit e01b23b84 is replacing
enable_sort with enable_groupagg in tests going forward where that's
the real intent. Re-introducing enable_sort here seems to go against
that goal.

> I plan to push this and backpatch through 14, adjusting the expected
> file per branch along the lines you described.

Also I don't understand why v5 is still creating new tables rather
than using existing tables in the tests.

- Richard

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2026-09-11 02:35:22 RE: START_REPLICATION silently truncates an overlong LSN component
Previous Message Alexander Korotkov 2026-09-10 21:54:46 Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation