| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Peter Praxmarer <ppraxmarer(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev |
| Date: | 2025-08-07 19:54:07 |
| Message-ID: | CAKFQuwaDxSDPKVF1bTxC2-CrF0MVi=x1yEhJA3RfAgkKt1mK6Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Aug 7, 2025 at 12:44 PM Peter Praxmarer <ppraxmarer(at)gmail(dot)com>
wrote:
>
> I have discovered what appears to be a severe bug in a development version
> of PostgreSQL 17 where a populated RECORD variable incorrectly fails an IS
> NOT NULL check.
>
>
Working as documented. You probably want to test: NOT (r IS NULL)
https://www.postgresql.org/docs/current/functions-comparison.html
If the expression is row-valued, then IS NULL is true when the row
expression itself is null or when all the row's fields are null, while IS
NOT NULL is true when the row expression itself is non-null and all the
row's fields are non-null.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2025-08-07 19:56:35 | BUG #19015: insert-returning failure: stable function in select policy doesn't see before-insert trigger change |
| Previous Message | Tom Lane | 2025-08-07 19:53:55 | Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev |