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 1g0q8Z-0001J3-LG for pgsql-hackers@arkaria.postgresql.org; Fri, 14 Sep 2018 15:36: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 1g0q8X-0006bl-Oy for pgsql-hackers@arkaria.postgresql.org; Fri, 14 Sep 2018 15:36:01 +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 1g0q8X-0006bZ-ED for pgsql-hackers@lists.postgresql.org; Fri, 14 Sep 2018 15:36:01 +0000 Received: from mail-qt0-x243.google.com ([2607:f8b0:400d:c0d::243]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1g0q8U-0005GK-Gb for pgsql-hackers@lists.postgresql.org; Fri, 14 Sep 2018 15:36:00 +0000 Received: by mail-qt0-x243.google.com with SMTP id z8-v6so9085732qto.9 for ; Fri, 14 Sep 2018 08:35:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=bbNONLz+NnT+GHSVIou+L1oZkM0voE2e+bMUCKTipzU=; b=n3gyfc7mgya3/exASz/P7S9mCKXX25O7EL3dANM/vZqQfVEMxIgM4XTksuLH7AWi9n hpsJPd+2sh9Xj44V9eDId8VDoK9BhWuooW7SastMq5tSZAHM+S888HYEvXqnRMqc1Ep8 mo7MhwvrgfDcBZhsYB//EOLNBdoqAeMUhfCDeTYvaUSD2n1sZv+w/Az44gK/Ec+e/mrQ zDSauVQJKX5dL/NyFolhbhxsRX211HcVOJAtaBndAkYbRBiEbrQ38s1p5aMtuRtM/ynT yFEwoqVp/RQh9ltNPyoLjvqSo+eKZLyJJhzqp3Y/KJH8SBZIBZonJxJukzVOGTFvN+Gz P5aQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=bbNONLz+NnT+GHSVIou+L1oZkM0voE2e+bMUCKTipzU=; b=Oj1gIzgt8wTV1Tlr9VCYAJvbVe1zMkXzBIIV7Vrl+zB23u4SyysiT6b1Lp2IC2cw0B 2n1Z1GtusJXYeds58b0QQI1b+7TdshiT+DX3/+hWQa8K5mH+HTYlQlheWTxUT+crSrdf 5DkAZbh9jVcR/jPz++Px2WSufb/1CnF3cVdPNwUHuMssA+Dtzf1tbFAoV1ByD/Ifh6tT EkjLK8mo0zaUEe80yvL4nvf5ejFZKuKol2s1h366vrSG1W8qjf/tVkmOowX2rIECi80r Ih1YZwqGv5EU6H7uj+LyneJdQ9BIFsIeqC74xwFRqVGApvua4YoVxZ++oPd7ChnqfV4b mf0w== X-Gm-Message-State: APzg51CSNvJQjp9mPR7gEyas2ewiNKLxyNc8xlGtjVqr5jFKjj3mdkv6 ZUOOx41BI5jPHtqQ4sLli0uYWYU7FULgOIEGDqzLmnFeRBuAqT/HHAb6Ce4J47qIPBkdr9lxuaW LN3XlXC2fAbwp7N+FnEyUArM2mw/ot7E2AdHxy5NgP53nA0bRlL9EBtLoIrswlCOBcB0T1S2PJ5 B5kySCjTizS9OXqQ== X-Google-Smtp-Source: ANB0Vdb1L53FYUj/ouvA8lAPW606upLXFp8e+ucq0+BZoM49cT9c36mpM4nM6wURXTZCsZVcXRyvtA== X-Received: by 2002:a0c:f50f:: with SMTP id j15-v6mr9539663qvm.157.1536939356717; Fri, 14 Sep 2018 08:35:56 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id g37-v6sm6189973qte.36.2018.09.14.08.35.56 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 14 Sep 2018 08:35:56 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id B9B16689; Fri, 14 Sep 2018 12:35:54 -0300 (-03) Date: Fri, 14 Sep 2018 12:35:54 -0300 From: Alvaro Herrera To: Michael Paquier Cc: pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru Message-ID: <20180914153554.562muwr3uwujno75@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2018-Sep-13, Michael Paquier wrote: > Improve autovacuum logging for aggressive and anti-wraparound runs > > 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. Hmm, can a for-wraparound vacuum really not be aggressive? I think one of those four cases is really dead code. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services