Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: using index or check in ALTER TABLE SET NOT NULL
Date
Msg-id 7554.1552497540@sss.pgh.pa.us
Whole thread Raw
In response to Re: using index or check in ALTER TABLE SET NOT NULL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: using index or check in ALTER TABLE SET NOT NULL
List pgsql-hackers
Tree view 
I wrote:
> Sergei Kornilov <sk@zsrv.org> writes:
>>> Ugh, I guess so. Or how about changing the message itself to use
>>> INFO, like we already do in QueuePartitionConstraintValidation?

>> Fine for me. But year ago this was implemented in my patch and Tom voted against using INFO level for such purpose:
https://www.postgresql.org/message-id/1142.1520362313%40sss.pgh.pa.us

> What I thought then was that you didn't need the message at all,
> at any debug level.  I still think that.

Oh, and yes, I think QueuePartitionConstraintValidation's usage
is an unacceptable abuse of INFO level.  I'm surprised we haven't
gotten complaints about it yet.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: hyrax vs. RelationBuildPartitionDesc
Next
From: Robert Haas
Date:
Subject: Re: using index or check in ALTER TABLE SET NOT NULL