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 1lAcv8-0005oT-2L for pgsql-bugs@arkaria.postgresql.org; Fri, 12 Feb 2021 18:11:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lAcv7-0007hn-0T for pgsql-bugs@arkaria.postgresql.org; Fri, 12 Feb 2021 18:11:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lAcv6-0007hg-Qk for pgsql-bugs@lists.postgresql.org; Fri, 12 Feb 2021 18:11:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lAcv4-0000iY-Sk for pgsql-bugs@lists.postgresql.org; Fri, 12 Feb 2021 18:11:55 +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 11CIBr4o1559356; Fri, 12 Feb 2021 13:11:53 -0500 From: Tom Lane To: =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16862: Unexpected result of checking for null "IS NOT NULL" in function In-reply-to: References: <16862-c10a7401d2973a9b@postgresql.org> <1552247.1613143392@sss.pgh.pa.us> Comments: In-reply-to =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= message dated "Fri, 12 Feb 2021 22:34:49 +0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1559354.1613153513.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 12 Feb 2021 13:11:53 -0500 Message-ID: <1559355.1613153513@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk =3D?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?=3D writes: > Does not work means does not produce the expected result. It seemed > obvious to me. If it were obvious I wouldn't be asking you for more information. You've left out a lot, like the table details and any sample data that might be necessary to reproduce the problem. The link I sent you offers some suggestions about how to create a self-contained problem report. Ideally, provide a SQL script that anyone can run in an empty database to see the misbehavior. Also, please keep the mailing list cc'd. I'm not the only developer who might take an interest in this problem, once we understand what it is. regards, tom lane