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 1o5uX0-0002Mh-P3 for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Jun 2022 19:36:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o5uWz-0004Nm-8j for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Jun 2022 19:36:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o5uWy-0004M6-Rh for pgsql-hackers@lists.postgresql.org; Mon, 27 Jun 2022 19:36:20 +0000 Received: from mail-qv1-xf34.google.com ([2607:f8b0:4864:20::f34]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o5uWr-0004CN-4b for pgsql-hackers@lists.postgresql.org; Mon, 27 Jun 2022 19:36:19 +0000 Received: by mail-qv1-xf34.google.com with SMTP id cs6so16399766qvb.6 for ; Mon, 27 Jun 2022 12:36:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=c57t/7MhrNPs/pz9FO8lR8EYGXPQFAiQDPitHV75IpI=; b=WkI6JyGRh0LvEIwG5uhANRCs+69blmHkHHqg5cc95LXPxttcUy2LZpjWPYZsC2NXmg 8H79zR/6qulXSPQfWMlE6uDQhxJnTsMNa+jSdz0a4bKl1YJVicxHh354FWhz9NQ9E5a7 O8DlqcCeS7Hf6QmDtqUzkcmh1CYLBSeSod8g3uk5Nvt4Dc751gxcEdDFEoKPDENm77w6 hOt5ga1LFkqcSONU/MmtH58jE7TvcFi75MZHM5zJgsyRADxOScT8Kftoh5PbX8RJCKLv h4P01kmP5FSEunFClnK4UIreOpQeMilDyiCP2W0VJy6CBnP8Lfw0EsowSAlx6BEF7SN6 a1Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=c57t/7MhrNPs/pz9FO8lR8EYGXPQFAiQDPitHV75IpI=; b=5LSJs31d9+92kYP9/9YCw3bHAU7xt2rZzP0UYE2JpxwoqCz4w9BOh8iGGFpnhxydrL Nby9ZNtRPyyvLVe1L+joLhc75HsU6QDtP8QMQS3hCp0a68ZxKhpTNXzxjO3qfIYVUwcM XBukl6Q+JeGdAdgbpC8aTdeSYI8mMflLu1kvNYZGutjnWZZ9FGjxv31/GQQbDjRxTtkT HwZCobzxbgXaZPv6ZWYLem47HdzWxxA1tXdQOQmBb9KNr6XfBkhKYYEJHvJAp+VENXl7 +YLHm84jtj/xgyaBq9j+TFmuGMivhrFZZB8QwKulqSLEjnkiG2VdasfsL4nxRd4U3lpa FE0Q== X-Gm-Message-State: AJIora9B9GWe+YQ9vAWX3ZoqCg+rAL2Qgaz2cyzoQP3I8JG2zkBJz3Mk BxpBl15LWwS9MEV3XdC90QiZ5Q== X-Google-Smtp-Source: AGRyM1siRA8bLk9WLz5teC7bRhWhb1uFDE7ffuyUg3sYAAc4WQp5RYDwqUs+wQ+ukZ5CmwRFegV6Qw== X-Received: by 2002:a05:622a:187:b0:319:b2d:4aff with SMTP id s7-20020a05622a018700b003190b2d4affmr8448085qtw.386.1656358572061; Mon, 27 Jun 2022 12:36:12 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id o1-20020a05620a2a0100b006a79479657fsm10044712qkp.108.2022.06.27.12.36.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jun 2022 12:36:10 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 0E9BC80079C; Mon, 27 Jun 2022 14:36:10 -0500 (CDT) Date: Mon, 27 Jun 2022 14:36:09 -0500 From: Justin Pryzby To: Robert Haas Cc: Andres Freund , Peter Geoghegan , John Naylor , pgsql-hackers@lists.postgresql.org, Hannu Krosing Subject: Re: do only critical work during single-user vacuum? Message-ID: <20220627193609.GB19662@telsasoft.com> References: <20211210015616.o242b4xchhpglfcy@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Feb 03, 2022 at 01:05:50PM -0500, Robert Haas wrote: > On Thu, Dec 9, 2021 at 8:56 PM Andres Freund wrote: > > I think we should move *away* from single user mode, rather than the > > opposite. It's a substantial code burden and it's hard to use. > > Yes. This thread seems to be largely devoted to the topic of making > single-user vacuum work better, but I don't see anyone asking the > question "why do we have a message that tells people to vacuum in > single user mode in the first place?". It's basically bad advice, > The correct thing to do would be to remove > the hint as bad advice that we never should have offered in the first > place. And so here. We should not try to make vacuum in single > user-mode work better or differently, or at least that shouldn't be > our primary objective. We should just stop telling people to do it. We > should probably add messages and documentation *discouraging* the use > of single user mode for recovering from wraparound trouble, exactly > the opposite of what we do now. There's nothing we can do in > single-user mode that we can't do equally well in multi-user mode. If > people try to fix wraparound problems in multi-user mode, they still > have read-only access to their database, they can use parallelism, > they can use command line utilities like vacuumdb, and they can use > psql which has line editing and allows remote access and is a way > nicer user experience than running postgres --single. We need a really > compelling reason to tell people to give up all those advantages, and > there is no such reason. It makes just as much sense as telling people > to deal with wraparound problems by angering a live anaconda. By chance, I came across this prior thread which advocated the same thing in a initially (rather than indirectly as in this year's thread). https://www.postgresql.org/message-id/flat/CAMT0RQTmRj_Egtmre6fbiMA9E2hM3BsLULiV8W00stwa3URvzA%40mail.gmail.com |We should stop telling users to "vacuum that database in single-user mode"