Re: BUG #18465: Wrong results from SELECT DISTINCT MIN in scalar subquery using HashAggregate

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: mtakahar(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18465: Wrong results from SELECT DISTINCT MIN in scalar subquery using HashAggregate
Date: 2024-05-18 14:18:01
Message-ID: 20240518141801.cobd5aup2pnogeo2@ddolgov.remote.csb
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On Tue, May 14, 2024 at 09:14:34PM +0000, PG Bug reporting form wrote:
>
> postgres=# SELECT ( SELECT DISTINCT MIN( col_int ) FROM B AS
> SUBQUERY1_t1 WHERE SUBQUERY1_t1 .col_int = table1 .col_int ), table1
> .col_int FROM CC AS table1 ;
> min | col_int
> --------+---------
> <null> | <null>
> <null> | 1 <------- *** wrong ***
> <null> | 2
> (3 rows)
>
> postgres=# SELECT ( SELECT DISTINCT MIN( col_int ) FROM B AS
> SUBQUERY1_t1 WHERE SUBQUERY1_t1 .col_int = table1 .col_int ), table1
> .col_int FROM CC AS table1 ;
> min | col_int
> -----+---------
> 1 | 1 <------- *** correct ***
> 1 | 2 <------- *** wrong ***
> 1 | <null> <------- *** wrong ***
> (3 rows)

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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Martijn Wallet 2024-05-18 14:47:29 Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
Previous Message Sandeep Thakkar 2024-05-18 14:09:24 Re: Issues in finding libeay.dll and ssleay.dll for win x64