From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: cataloguing NOT NULL constraints
Date: Fri, 07 Apr 2023 18:26:28 -0400
Message-ID: <3248613.1680906388@sss.pgh.pa.us> (raw)
In-Reply-To: <20230407222326.54ng3j4phv3es3s3@awork3.anarazel.de>
References: <20230407211000.d2iaklm76djy26nm@awork3.anarazel.de>
<20230407211155.qrc2bqgyogvrfkzo@alvherre.pgsql>
<20230407211950.aojbdirwdrxjeyzb@awork3.anarazel.de>
<3242330.1680903993@sss.pgh.pa.us>
<20230407222326.54ng3j4phv3es3s3@awork3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> On 2023-04-07 17:46:33 -0400, Tom Lane wrote:
>> After quickly eyeing the diffs, I'm just going to take the new output
>> as good. I'm not surprised that there are additional output messages
>> given the additional catalog entries this made. I *am* a bit surprised
>> that some messages seem to have disappeared --- are there places where
>> this resulted in fewer catalog accesses than before? Nonetheless,
>> there's no good reason to assume this test is exposing any bugs.
> I wonder if the issue is that the new paths miss a hook invocation.
Perhaps. I'm content to silence the buildfarm for today; we can
investigate more closely later.
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-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, alvherre@alvh.no-ip.org, pryzby@telsasoft.com, peter.eisentraut@enterprisedb.com, pgsql-hackers@lists.postgresql.org
Subject: Re: cataloguing NOT NULL constraints
In-Reply-To: <3248613.1680906388@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