From: Zu-Ming Jiang <zuming.jiang@inf.ethz.ch>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17982: Inconsistent results of SELECT with CTE caused by subquery comparison
Date: Mon, 19 Jun 2023 20:00:20 +0200
Message-ID: <5d183639-dbc5-e6be-39bd-6ada253c5ece@inf.ethz.ch> (raw)
In-Reply-To: <2980037.1687190927@sss.pgh.pa.us>
References: <17982-3fa239feecd6c1b3@postgresql.org>
<2980037.1687190927@sss.pgh.pa.us>
Thanks for your information and the fixing! I will then apply your patch
and test postgres again.
Best,
Zuming
------------------------------------------------------------------------
*From:* Tom Lane [mailto:tgl@sss.pgh.pa.us]
*Sent:* Monday, June 19, 2023 at 6:08 PM
*To:* zuming.jiang@inf.ethz.ch
*Cc:* pgsql-bugs@lists.postgresql.org
*Subject:* BUG #17982: Inconsistent results of SELECT with CTE caused by
subquery comparison
> PG Bug reporting form<noreply@postgresql.org> writes:
>> My fuzzer finds a correctness bug in Postgres, which makes Postgres return
>> inconsistent results.
> This appears to be the same issue you already reported in bug #17978.
> At least, the patch I just posted in that thread fixes this too.
>
> regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: zuming.jiang@inf.ethz.ch, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17982: Inconsistent results of SELECT with CTE caused by subquery comparison
In-Reply-To: <5d183639-dbc5-e6be-39bd-6ada253c5ece@inf.ethz.ch>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox