Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etHgx-0004QI-Mj for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Mar 2018 18:52:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etHgw-0004wO-K9 for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Mar 2018 18:52:02 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etHgw-0004wE-98 for pgsql-hackers@lists.postgresql.org; Tue, 06 Mar 2018 18:52:02 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etHgt-0006fq-1I for pgsql-hackers@postgresql.org; Tue, 06 Mar 2018 18:52:01 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w26Ipr9f001144; Tue, 6 Mar 2018 13:51:53 -0500 From: Tom Lane To: Sergei Kornilov cc: Alvaro Herrera , Ildar Musin , Stephen Frost , Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: using index or check in ALTER TABLE SET NOT NULL In-reply-to: <1715451520361128@web26o.yandex.ru> References: <880511520351578@web5j.yandex.ru> <20180306172528.xnelm3xcq2qeyd2g@alvherre.pgsql> <1715451520361128@web26o.yandex.ru> Comments: In-reply-to Sergei Kornilov message dated "Tue, 06 Mar 2018 21:32:08 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1141.1520362313.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 06 Mar 2018 13:51:53 -0500 Message-ID: <1142.1520362313@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Sergei Kornilov writes: >> ISTM that depending on DEBUG messages is bad because debugging lines >> added elsewhere will make your tests fail; > I agree and this is reason why i not used DEBUG message in tests as was = proposed. I found INFO messages in tests and decided that this was an acce= ptable option year ago. INFO is for user-facing messages, such as output from VACUUM VERBOSE, where the user has specifically requested the output. I do not think this falls into that category. Even if you persuade some committer to commit it like that, there will be user pushback asking us to get this noise out of their faces ... and then we'll have to find some other way to test it. Do you actually need test output proving that this code path was taken rather than the default one? Seems like looking at the code coverage report might be enough. > In this case we need remove INFO from ALTER TABLE ATTACH PARTITION code = and tests. I think is a bad idea of using different rules for same stuff, = right? Probably i can do this work too. I did not see any INFO messages in a quick test of ALTER TABLE ATTACH PARTITION, but if there are any lurking in there, they probably need to be downgraded. regards, tom lane