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 1g1s2A-00017h-LR for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Sep 2018 11:49:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g1s28-0001sv-Ha for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Sep 2018 11:49:40 +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 1g1s28-0001so-6T for pgsql-hackers@lists.postgresql.org; Mon, 17 Sep 2018 11:49:40 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g1s24-0001Sg-8R for pgsql-hackers@lists.postgresql.org; Mon, 17 Sep 2018 11:49:38 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 50693212A0; Mon, 17 Sep 2018 07:49:35 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 17 Sep 2018 07:49:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=QepvoY8r8mqE5wKBN6TEZ1dqFt3FgsQyEJ9ul+jO1tA=; b=jae8Tt4J xo5KEFqGg59AeJrGIc0zdNk41JVPhN+aa5x5CSAgPNZGhSXIem17f6YChhv9Nvw9 Xtc6ozFfS22Co6qQrf693BwkWUuqOz/+kTAFM3jIyuSXkor2vDDRi9ErjovC6y9G FdHL3jHY89oZOAZ/2K6NzxJsfpkJHkRGHmSF1DDh0iT+gUDnSjr7WLprWZDlgD/u +zqu6F08jqiwxgu7wfa+6bYC/zDmC/K1NEQPbrmCGO6AjCxo8qgqCTBF4e7HiGoZ 2U2Kh2mONYf1Xjl20wQpISy2nvFhymAu2Sen97eIYfX86nHF/DmQxPzwb5eNt+Wb iGw6eg6SX3VAhQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=QepvoY8r8mqE5wKBN6TEZ1dqFt3Fg sQyEJ9ul+jO1tA=; b=dnhkJDvdrkcKpUJVUb+N1RtGl2f0HpqFDWRb4AK6KDWdw PxdtP0F3sJ0Vg1Nq4tfRv2derAb4LMsGiIydgF2nRoZNDQm3wZhZXFRQTGrJo9cH LUfKw9lElOaKDWBy7cSvXuUdlYRGl5U+RqZKGPdIwqib/T6Yd2xN031y+Po5CQ0R tqHcfwJ6if0OS+pKzzvD1OH1iLlFDOQrNOdFAXTBFriTl+qD1m6AftN5EAv2QzmL n9X32dsqhn5t619zRH3Z6o1Ne1pX4HD+jhdZDGwnaTNcDhtkihfX//Q32l1SyLQf FWvIkbHNqfF12dnBosLcCvNsD6BrE6B+2bxa8gxRg== X-ME-Proxy: X-ME-Sender: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 73F3F102D5; Mon, 17 Sep 2018 07:49:33 -0400 (EDT) Date: Mon, 17 Sep 2018 20:49:30 +0900 From: Michael Paquier To: Alvaro Herrera Cc: pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru Message-ID: <20180917114930.GC31460@paquier.xyz> References: <20180914153554.562muwr3uwujno75@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LwW0XdcUbUexiWVK" Content-Disposition: inline In-Reply-To: <20180914153554.562muwr3uwujno75@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --LwW0XdcUbUexiWVK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 14, 2018 at 12:35:54PM -0300, Alvaro Herrera wrote: > On 2018-Sep-13, Michael Paquier wrote: >> Improve autovacuum logging for aggressive and anti-wraparound runs >>=20 >> A log message was being generated when log_min_duration is reached for >> autovacuum on a given relation to indicate if it was an aggressive run, >> and missed the point of mentioning if it is doing an anti-wrapround >> run. The log message generated is improved so as one, both or no extra >> details are added depending on the option set. >=20 > Hmm, can a for-wraparound vacuum really not be aggressive? I think one > of those four cases is really dead code. Sure, at the same time it is a no-brainer to keep the code as is, and seeing log messages where (!aggressive && wraparound) would be an indication of surrounding bugs, no? There have been issues in this area in the past. -- Michael --LwW0XdcUbUexiWVK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAluflMoACgkQnvQgOdby QH0UPQ/+M/QjhZ6GuOsSc/mEbRdDlz6UTLBudKuE+ndefqB69kdDVS5SJVOikNEW HGj0pA2JoxpVr3fSbfNsNFfi8sBS/J1egeRMc2fuqD1pK4XcGHRv1+6JRCK4s4Pm 0nNJZNacRP+6HSOr3fvsyeQYUrT2bEkt8Kra44saDds+riGEIxtB0YMHMZQW8NZh GFCu42xUkrmYZ0w4d4zyv7v83Qd6yL2ZLc9m246mR+eG1ZxlAOMK7yVVTJZISbri OVrIQqp1O/g0Y9cs9+pzRGRmGcoFdGPgRNDoY4t9QXK7jNG2brESGGzW63eptt6u I1CcBEMu/hKGnZ8MvNjioYppGD/ffxUblt/Ha/EuOFwiVKmRnZALk/Wl4RHMAj+y jjifU+9E+Xik1N0AyiEn183oJ7swflRNAckWZvXiRDJyKF5ePlbpjxfnBHgTY/Td k/EIABNA+f5up/8z+4qF4W4ya+r7t/2+GxtFxaVKmWxMhLOv0hPKe8aRdthSzch6 ctBwtSDnCAPRUF/v5cvQiV4IHmKkmOVTFBeiKCVsuUIJxM9oEjTYZ+lkO+WRnJwn Pw+quiwg/cT7AtlgmBHDNjmuY1lAdHXCnaUCpMODdbOTAvQcbFgcpsFoLceAXqS2 1iSHRTItV99p2uenvUDXFWKlJv8/PRenh32TI/e+OUJAnuOBd8Y= =7xjm -----END PGP SIGNATURE----- --LwW0XdcUbUexiWVK--