agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedFrom: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: jbe-mlist@magnetkern.de, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Subject: Re: Parameter NOT NULL to CREATE DOMAIN not the same as CHECK (VALUE IS NOT NULL)
Date: Wed, 08 Jan 2025 16:24:34 -0500
Message-ID: <1694911.1736371474@sss.pgh.pa.us> (raw)
In-Reply-To: <Z37p0paENWWUarj-@momjian.us>
References: <173591158454.714.7664064332419606037@wrigleys.postgresql.org>
<Z37p0paENWWUarj-@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> I think this needs some serious research.
We've discussed this topic before. The spec's definition of IS [NOT]
NULL for composite values is bizarre to say the least. I think
there's been an intentional choice to keep most NOT NULL checks
"simple", that is we look at the overall value's isnull bit and
don't probe any deeper than that.
If the optimizations added in v17 changed existing behavior,
I agree that's bad. We should probably fix it so that those
are only applied when argisrow is false.
regards, tom lane
view thread (6+ messages) latest in thread
Message-ID: <1694911.1736371474@sss.pgh.pa.us>
Permalink: ../1694911.1736371474@sss.pgh.pa.us/
Also on: postgresql.org/message-id/1694911.1736371474@sss.pgh.pa.us
reply
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, pgsql-hackers@lists.postgresql.org
Subject: Re: Parameter NOT NULL to CREATE DOMAIN not the same as CHECK (VALUE IS NOT NULL)
In-Reply-To: <1694911.1736371474@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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox