Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qBHR0-00061V-5K for pgsql-bugs@arkaria.postgresql.org; Mon, 19 Jun 2023 16:08:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qBHQz-0004gi-1U for pgsql-bugs@arkaria.postgresql.org; Mon, 19 Jun 2023 16:08:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qBHQy-0004gY-QH for pgsql-bugs@lists.postgresql.org; Mon, 19 Jun 2023 16:08:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qBHQw-003S88-DG for pgsql-bugs@lists.postgresql.org; Mon, 19 Jun 2023 16:08:52 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 35JG8lMi2980038; Mon, 19 Jun 2023 12:08:47 -0400 From: Tom Lane To: zuming.jiang@inf.ethz.ch cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17982: Inconsistent results of SELECT with CTE caused by subquery comparison In-reply-to: <17982-3fa239feecd6c1b3@postgresql.org> References: <17982-3fa239feecd6c1b3@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 19 Jun 2023 12:07:42 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2980036.1687190927.1@sss.pgh.pa.us> Date: Mon, 19 Jun 2023 12:08:47 -0400 Message-ID: <2980037.1687190927@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form 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