Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7LSi-0001sO-4Q for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Oct 2018 14:15:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g7LSf-0000pt-RH for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Oct 2018 14:15:41 +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 1g7LSf-0000pl-GF for pgsql-hackers@lists.postgresql.org; Tue, 02 Oct 2018 14:15:41 +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 1g7LSc-0003Pd-Vp for pgsql-hackers@lists.postgresql.org; Tue, 02 Oct 2018 14:15:40 +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 w92EFSIU000339; Tue, 2 Oct 2018 10:15:28 -0400 From: Tom Lane To: Michael Paquier cc: Masahiko Sawada , Alvaro Herrera , Sergei Kornilov , nasbyj@amazon.com, Andres Freund , Robert Haas , PostgreSQL Hackers Subject: Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru In-reply-to: <20181002065508.GC17642@paquier.xyz> References: <23209391537822541@iva4-6d7004ac8463.qloud-c.yandex.net> <20180924211117.tpwxemzd3372nagj@alvherre.pgsql> <20181002001151.GP11712@paquier.xyz> <20181002065508.GC17642@paquier.xyz> Comments: In-reply-to Michael Paquier message dated "Tue, 02 Oct 2018 15:55:08 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <337.1538489728.1@sss.pgh.pa.us> Date: Tue, 02 Oct 2018 10:15:28 -0400 Message-ID: <338.1538489728@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Michael Paquier writes: > My brain is rather fried for the rest of the day... But we could just > be looking at using USE_ASSERT_CHECKING. Thoughts from other are > welcome. I'd go with folding the condition into a plain Assert. Then it's obvious that no code is added in a non-assert build. I can see that some cases might be so complicated that that isn't nice, but this case doesn't seem to qualify. regards, tom lane