From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Dolgov <9erthalion6@gmail.com>
cc: mtakahar@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18465: Wrong results from SELECT DISTINCT MIN in scalar
 subquery using HashAggregate
In-reply-to: <20240518141801.cobd5aup2pnogeo2@ddolgov.remote.csb>
References: <18465-2fae927718976b22@postgresql.org>
 <20240518141801.cobd5aup2pnogeo2@ddolgov.remote.csb>
Comments: In-reply-to Dmitry Dolgov <9erthalion6@gmail.com>
	message dated "Sat, 18 May 2024 16:18:01 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2787679.1716051404.1@sss.pgh.pa.us>
Date: Sat, 18 May 2024 12:56:44 -0400
Message-ID: <2787680.1716051404@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2787680.1716051404%40sss.pgh.pa.us>
Precedence: bulk

Dmitry Dolgov <9erthalion6@gmail.com> writes:
> Thanks, I could reproduce this in v15 and v16. Interestingly enough it
> was fixed in d0d44049d1, but looks like due to lack of error reports the
> fix was applied only on the main branch. I assume this one makes it
> necessary to back-patch the fix.

Hah.  Nothing like fixing a bug that you know is there but you can't
demonstrate it ;-).  I confirm the problem appears in d0d44049d1^
(and at least as far back as v12), but not in d0d44049d1 or HEAD.
So yeah, add test case and back-patch.

Many thanks for the test case!

			regards, tom lane