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-10 00:10:33
Message-ID: CAMbWs4-bwvBadtS83LJw5_BnxNonY4YA9DRfEKK8NHpgtxHruw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Sep 10, 2026 at 7:40 AM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> I've revised the patch. The v3 changes are:
> 1. The test now covers the hash path as well. v2 turned
> enable_hashagg off, which is precisely the plan shape that was not
> broken in isolation; both strategies are now exercised, each with its
> plan and its result.

I think it'd better to resue existing tables rather than create
new ones for the tests. Maybe we can reuse test1cs/test1ci,
test2cs/test2ci, test3cs/test3ci to reproduce this issue?

Also on master we have this new GUC enable_groupagg. Maybe it'd
better to use that instead of enable_sort?

- Richard

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Alexander Korotkov 2026-09-09 22:39:42 Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation