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

From Richard Guo
Subject Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
Date
Msg-id CAMbWs4_fV6BjBDaBi8QZ36OrApo-65JMti=2zGqbwUkb0mjdVQ@mail.gmail.com
Whole thread
In response to BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: Bug in heap_get_root_tuples
List pgsql-bugs
On Fri, Sep 11, 2026 at 6:54 AM Alexander Korotkov <aekorotkov@gmail.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



pgsql-bugs by date:

Previous
From: Andrey Rachitskiy
Date:
Subject: Re: BUG #19671: IPv4 CIDR Prefix Integer Overflow Bypasses Validation in inet/cidr Casts
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: START_REPLICATION silently truncates an overlong LSN component