Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h9sPR-0006ok-2K for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Mar 2019 14:23:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h9sPP-0005KK-NS for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Mar 2019 14:23:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h9sPP-0005KD-Eb for pgsql-hackers@lists.postgresql.org; Fri, 29 Mar 2019 14:23:03 +0000 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h9sPM-0000dE-Ak for pgsql-hackers@lists.postgresql.org; Fri, 29 Mar 2019 14:23:03 +0000 Received: by mail-qt1-x844.google.com with SMTP id d13so2748916qth.5 for ; Fri, 29 Mar 2019 07:23:00 -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=i4FCPaIhNHZlFiX/cea+6xZHo/d4BIekhTKZE0TJdxk=; b=N2nm1+3GynrSp6+z5Fh6qwFSnMKjTcSk6Jglph1PUAYpPA4tvbr+YFJ4Jb9WUJu3Ow Tu+Jur7ltcy4WvNSITfzOEowuxJYlZ/o8VXqyhKW+z2FPrf9EQQOV02aNWu0IVXKG8D4 EzDXlY6PWuejjQaX/GKStfTrrpzPCoKoYUBOKhKULnpiHpl5PgS1535TaPwEWRndthoi KtvmmXzTR8ZVSymy33r5o2AV0vRIWX+NQtwQ97pfFGA17cq3ggFQMkYRHjWZcd3I9J37 0a07N/GTOBHaecuIsJ2gY3BBl0SqypItUfSqYoo5O9qshS4As4KlQWX6OrkKvRl4FXbN gCrw== 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=i4FCPaIhNHZlFiX/cea+6xZHo/d4BIekhTKZE0TJdxk=; b=N6QZsgegOSQ4fhNA5JE+W6B5xogACR5SxgbTuYhZWDwjO4zSlxzNj1JRi6vdAwiuGa G7A4FhKxAe6NNQtoauVdng5DaRkRtEbr93y55HQtj/N5zs5qfKRO04GMHAOgRhS77jG/ Kw8PInIutlBvhU7fho2SMMeF3F0LjUAZ5sUMGSkhcpoE0Zk22JVBLPsBIucd+f7qNrgQ 7mLK+SIWl0i3ny7na5AD3ZI6zb5iHKB7UeRh4UT5AWQu2QPNVRvXbUEoRc+dmEEKg1mU 6o0+VPi2+Kp2bvHix641Rxu5EVYAjmgyedGMljFCb8iOSTIUo9zIZpYQeYW1mY0T81dp uqDA== X-Gm-Message-State: APjAAAVyH1rRbbdhGJzT34qVc6YrAi40k2uy5N1J67JstJko8CcorebM OBeieFWaFwbR0BkZ2SrfVJ4+Kg== X-Google-Smtp-Source: APXvYqznKGhOmmDhq+cSG2S+kO0c57uxWbYXusp3aRG4yF7Dyht/AnwHag3O832YW4NAk6QlHGL2ZQ== X-Received: by 2002:a0c:9e0f:: with SMTP id p15mr34318146qve.178.1553869378735; Fri, 29 Mar 2019 07:22:58 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id n3sm1181979qkf.93.2019.03.29.07.22.57 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 29 Mar 2019 07:22:57 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 7B8D7120A6D; Fri, 29 Mar 2019 11:22:55 -0300 (-03) Date: Fri, 29 Mar 2019 11:22:55 -0300 From: Alvaro Herrera To: Michael Paquier Cc: Andrew Dunstan , Kyotaro HORIGUCHI , sawada.mshk@gmail.com, tgl@sss.pgh.pa.us, sk@zsrv.org, nasbyj@amazon.com, andres@anarazel.de, robertmhaas@gmail.com, pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru Message-ID: <20190329142255.GA22447@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190329140349.GI1954@paquier.xyz> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Mar-29, Michael Paquier wrote: > On Fri, Mar 29, 2019 at 09:11:47AM -0400, Andrew Dunstan wrote: > > +                (errmsg_internal("found vacuum to prevent wraparound of > > table \"%s.%s.%s\" to be not aggressive, so skipping", > > > > This might convey something to hackers, but I doubt it will convey much > > to regular users. Perhaps something like "skipping redundant > > anti-wraparound vacuum of table ..." would be better. > > "skipping redundant" is much better. Yeah, that looks good to me too. I wonder if we really need it as LOG though; we don't say anything for actions unless they take more than the min duration, so why say something for a no-op that takes almost no time? Maybe make it DEBUG1. > > The comment is also a bit too tentative. Perhaps something like this > > would do: > > > > Normally the relfrozenxid for an anti-wraparound vacuum will be old > > enough to force an aggressive vacuum. However, a concurrent vacuum > > might have already done this work that the relfroxzenxid in relcache > > has been updated. If that happens this vacuum is redundant, so skip it. > > That works for me. s/relfroxzenxid/relfrozenxid/ -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services