From: Tom Lane <tgl@sss.pgh.pa.us>
To: Дмитрий Иванов <firstdismay@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16862: Unexpected result of checking for null "IS NOT NULL" in function
Date: Fri, 12 Feb 2021 13:11:53 -0500
Message-ID: <1559355.1613153513@sss.pgh.pa.us> (raw)
In-Reply-To: <CAPL5KHp_+TBshAc+RPwWUdULqfENa367Xnye8nvCHgNcd3RfEw@mail.gmail.com>
References: <16862-c10a7401d2973a9b@postgresql.org>
<1552247.1613143392@sss.pgh.pa.us>
<CAPL5KHp_+TBshAc+RPwWUdULqfENa367Xnye8nvCHgNcd3RfEw@mail.gmail.com>
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= <firstdismay@gmail.com> 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
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: tgl@sss.pgh.pa.us, firstdismay@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16862: Unexpected result of checking for null "IS NOT NULL" in function
In-Reply-To: <1559355.1613153513@sss.pgh.pa.us>
* 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