Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p73Ut-0007P6-2Z for pgsql-bugs@arkaria.postgresql.org; Sun, 18 Dec 2022 23:55:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p73Uq-0000sO-SL for pgsql-bugs@arkaria.postgresql.org; Sun, 18 Dec 2022 23:55:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p73Uq-0000sE-IQ for pgsql-bugs@lists.postgresql.org; Sun, 18 Dec 2022 23:55:08 +0000 Received: from mail-pj1-x102a.google.com ([2607:f8b0:4864:20::102a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p73Un-0007EX-NE for pgsql-bugs@lists.postgresql.org; Sun, 18 Dec 2022 23:55:08 +0000 Received: by mail-pj1-x102a.google.com with SMTP id u15-20020a17090a3fcf00b002191825cf02so7353024pjm.2 for ; Sun, 18 Dec 2022 15:55:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=d9MVlCWtXr+yMN5gS0U1va7piBw6C3Egp2DobPk9J/o=; b=RWY7Zcpp0B3oPIVCxmxzU93fsJ8S1AIRgLdO/fydZPhGBy2Yc2KLKmOCdYAFGXsS+a Rcg+uLq5m4Vg/Vcajnt39YuodX8cDS0+CBxrSmLpefsQS1bEl1TwTF9Blfm9dJewN5Br FF/Q9TUaACrfALPQC+u+v2u7mYsUGmb+WxBtYlp3ZGG1vKEi5eNATofE3Cjb5fyKeQSl bvl3oDWwtK16r/4+sUFpUVqKFUgvuT0c8Hw7PMrQRE1Wtcx7wodJ9+ZRoRPJppfKJOL+ Wi2tTmXAtljJ/JtUJvjQ6oyWODy16MSZa1luvGAjLrZd6eJnomEKjiE0NIzJRPmXn4ZU WCiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=d9MVlCWtXr+yMN5gS0U1va7piBw6C3Egp2DobPk9J/o=; b=quxpINW82tWRycckOVBJFi7lsZjjOAIIVce9uNJR2YbNo9mjL+kMbFGK2V+Mi8R7tU UabD2BSJ7CyJxODGvr7ngxxIV3QtgFJXpGPsRWxcX0uzUxnvln1e9IDqnCFZOk4TQ3d4 hFFgN1QI3uyx/70YLrZJIV3JA37CrsGLnXlsFZjjgD37jJ4DRYet45d6HQVgaeFOUZEA wfBBNyLj+aqJuLYS2b5LTKenQNvOn5oBjusS5i0A66y6JbNUXQM7adnqrvW+67MnIFrp GIry5Q5p9nZBY9WfepquipFQSO8EeVS3Ou11DSF4QmAkyhaxRuftGfUYfID1CFag/WdP amTQ== X-Gm-Message-State: ANoB5pm2twSMuz1Hm9cpnJm8ubVvMl9u7x64ZaGuV53mVDy4lOWoEAA7 AOk8FDY5EVERO52L2neObOM= X-Google-Smtp-Source: AA0mqf6UeAdChsh5vvwSw6qtO6iWpB3hYxsF4Z32shU+rCaSthYvP4hFPVqLc2tCbSrlALyPAX//wg== X-Received: by 2002:a17:902:dac3:b0:189:62f7:e5fc with SMTP id q3-20020a170902dac300b0018962f7e5fcmr55739960plx.14.1671407703204; Sun, 18 Dec 2022 15:55:03 -0800 (PST) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id m12-20020a170902768c00b00189327b022bsm5573094pll.286.2022.12.18.15.55.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 18 Dec 2022 15:55:02 -0800 (PST) Date: Sun, 18 Dec 2022 15:55:00 -0800 From: Nathan Bossart To: Peter Geoghegan Cc: Tom Lane , postgresql@taljaren.se, pgsql-bugs@lists.postgresql.org, Michael Paquier Subject: Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue) Message-ID: <20221218235500.GC1476904@nathanxps13> References: <17717-6c50eb1c7d23a886@postgresql.org> <3439037.1671130590@sss.pgh.pa.us> <3544447.1671141436@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Dec 15, 2022 at 08:39:54PM -0800, Peter Geoghegan wrote: > On Thu, Dec 15, 2022 at 1:57 PM Tom Lane wrote: >> I could get behind manual VACUUM not invoking vac_update_datfrozenxid >> by default, perhaps. But if it can never call it, then that is a >> fairly important bit of housekeeping that is unreachable except by >> autovacuum. No doubt the people who turn off autovacuum are benighted, >> but they're still out there. > > I wouldn't mind adding another option for this to VACUUM. We already > have a couple of VACUUM options that are only really needed as escape > hatches, or perhaps as testing tools used by individual Postgres > hackers. Another one doesn't seem too bad. The VACUUM command should > eventually become totally niche, so I'm not too concerned about going > overboard here. Perhaps there could also be an update-datfrozenxid function that vacuumdb calls when finished with a database. Even if vacuum becomes smarter about calling vac_update_datfrozenxid, this might still be worth doing. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com