| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Дмитрий Иванов <firstdismay(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16862: Unexpected result of checking for null "IS NOT NULL" in function |
| Date: | 2021-02-12 18:11:53 |
| Message-ID: | 1559355.1613153513@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= <firstdismay(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luka Žitnik | 2021-02-12 18:14:17 | Unexpected serialization error |
| Previous Message | Tom Lane | 2021-02-12 15:23:12 | Re: BUG #16862: Unexpected result of checking for null "IS NOT NULL" in function |