Re: using index or check in ALTER TABLE SET NOT NULL - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: using index or check in ALTER TABLE SET NOT NULL
Date
Msg-id 20190802195438.4vuotpz6pdq6r6jg@development
Whole thread Raw
In response to Re: using index or check in ALTER TABLE SET NOT NULL  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: using index or check in ALTER TABLE SET NOT NULL
List pgsql-hackers
On Wed, Jun 12, 2019 at 08:34:57AM +1200, David Rowley wrote:
>On Tue, 11 Jun 2019 at 03:35, Sergei Kornilov <sk@zsrv.org> wrote:
>> > Does anyone think we shouldn't change the INFO message in ATTACH
>> > PARTITION to a DEBUG1 in PG12?
>>
>> Seems no one wants to vote against this change.
>
>I'm concerned about two things:
>
>1. The patch reduces the test coverage of ATTACH PARTITION. We now
>have no way to ensure the constraint was used to validate the rows in
>the partition.
>2. We're inconsistent with what we do for SET NOT NULL and ATTACH
>PARTITION. We raise an INFO message when we use a constraint for
>ATTACH PARTITION and only a DEBUG1 for SET NOT NULL.
>
>Unfortunately, my two concerns conflict with each other.
>

We're getting close to beta3/rc1, and this thread was idle for ~1 month.

I think there's a consensus to change INFO to DEBUG1 in pg12, and then
maybe imlpement something like VERBOSE mode in the future. Objections?

As for the reduction of test coverage, can't we deduce whether a
constraint was used from data in pg_stats or something like that?

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services 



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: The unused_oids script should have a reminder to use the8000-8999 OID range
Next
From: Tom Lane
Date:
Subject: Re: using index or check in ALTER TABLE SET NOT NULL