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 1pmGvl-0004DF-4u for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Apr 2023 16:33:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pmGvj-0007Dx-PV for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Apr 2023 16:33:15 +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 1pmGvj-0007Dn-CJ for pgsql-hackers@lists.postgresql.org; Tue, 11 Apr 2023 16:33:15 +0000 Received: from mail-il1-x132.google.com ([2607:f8b0:4864:20::132]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pmGvb-002GOT-SB for pgsql-hackers@postgresql.org; Tue, 11 Apr 2023 16:33:14 +0000 Received: by mail-il1-x132.google.com with SMTP id b7so2842422ilm.4 for ; Tue, 11 Apr 2023 09:33:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; t=1681230786; 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=Q174RMDQsbB3VZE1OEH0p9gS4ObRK/0kGEdMvF8yuTk=; b=DjNwJGORGRr0R78r0ox3yOSSJAOLRyQPyN3Tz0ibEqcxolFTvw7ZIMsaPQ/fKVXXiS a1frMuWc9Zadb5D6LbYWJDmrsDQQk8eju6GPG0uKFMDO9VgMTgXEeGIV5qZG6BzkG2A7 6Zof+k8LYxI1THeDrI9/2Wzrfj2ltKDSHGyzKNt7loesRfHbCFzCDMHTzV4U7KWEs4tL Ae0+LKo3ooftL7z+U9nw1vtmopMTQFRW40HTnZebH7Xxy9fAvfRtbxtpQosgEcFNhfrW HisHIOZRmJxgfJZu2PzXQR4xtdwjInNGFdHmzTPjBFOPyvQxByfcQ6h3sYllWdC/im1w 9T/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681230786; 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=Q174RMDQsbB3VZE1OEH0p9gS4ObRK/0kGEdMvF8yuTk=; b=dlo0fUMEKcKP7W9QosXPrXeoFayld0jVg10DeFproilqg6olCwRBDp35sa8xKi2+Ni I1Xy0Qmh93Ja9Tdr5j2D47Jjfm64NstakGwQvlaFKj8YWrENPHXC7z9lJYRfq/09ldZD cgP3IYGoCjcT2dBn4Z71LWtd5uXedbXnqgGcLgrex+D98sfKYdC5vn5fSi5sASpX3DVq DFrXMl9DzGZKGoU1iGUiKT/rEqfFG5f0UL/+RiuomIUCe02AmBV4bdUnzuxugH7m1Di6 W4Zmf31FhWmBOAzaLkJ76BLsSzBN/7jtDEYoKGh+EQ2nVXlhjrIxrIIhWN0OaHB7UhYd rKYQ== X-Gm-Message-State: AAQBX9ceWYtu0X/PD41a4gr3lVVqYTgn71c3EdpgMqXKWTSbd+56TbZa uHGmp1mh8MVL1eVGf6q7N4Gcpw== X-Google-Smtp-Source: AKy350ag9nBJnHVua+773moTLgx5GQ6DdcaPowkC5wlmNV0B2YruDs8gRIwTjwOX6VeA7yPKVebuBg== X-Received: by 2002:a92:6912:0:b0:317:980d:970 with SMTP id e18-20020a926912000000b00317980d0970mr8384184ilc.7.1681230785941; Tue, 11 Apr 2023 09:33:05 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id y32-20020a029523000000b0040bd91e4803sm1039284jah.155.2023.04.11.09.33.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Apr 2023 09:33:03 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id E5C0E8008DF; Tue, 11 Apr 2023 11:33:01 -0500 (CDT) Date: Tue, 11 Apr 2023 11:33:01 -0500 From: Justin Pryzby To: Andres Freund Cc: Alvaro Herrera , pgsql-hackers@postgresql.org Subject: Re: Should we remove vacuum_defer_cleanup_age? Message-ID: References: <20230317230930.nhsgk3qfk7f4axls@awork3.anarazel.de> <20230318093357.g4e3eexqg6dxmuel@alvherre.pgsql> <20230322170048.ffbnfr5o2jrjgb2f@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230322170048.ffbnfr5o2jrjgb2f@awork3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Mar 22, 2023 at 10:00:48AM -0700, Andres Freund wrote: > I don't know whether others think we should apply it this release, given the > "late submission", but I tend to think it's not worth caring the complication > of vacuum_defer_cleanup_age forward. I don't see any utility in waiting; it just makes the process of removing it take longer for no reason. As long as it's done before the betas, it seems completely reasonable to remove it for v16. -- Justin