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 1mFgBe-000442-M6 for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Aug 2021 17:14:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mFgBb-0003Ei-TD for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Aug 2021 17:14:07 +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 1mFgBb-0003Ea-LN for pgsql-hackers@lists.postgresql.org; Mon, 16 Aug 2021 17:14:07 +0000 Received: from new3-smtp.messagingengine.com ([66.111.4.229]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mFgBY-0001cB-E7 for pgsql-hackers@lists.postgresql.org; Mon, 16 Aug 2021 17:14:06 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 243395803F8; Mon, 16 Aug 2021 13:14:03 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 16 Aug 2021 13:14:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=W4LJOgjmCmsdrnXHG7X5KvFlXYc5pC6Ev5sliqKP+VQ=; b=TRMC1+8Z 6UNOwfnm4QlMRUk23/SvFrw03amNu5lVrEX4JIAzARG4r042YnTk9MguqNC7SH5g qUDEKh4p8IsRs97Qv8T7o39H0ijfVJVVzPpcFO3ZK6eIq+sLr0s8sClgBR+1rh4Y xKnb3le036165nlvIln2EMFg7IYAwzP9E+ezs+iGpnvoj+AMsHj7vlZaFVL+UU7P z7F9sNsLH2C+QvchvNyDT7CZ5ykageiAeWQPuBtALA9yW1lJ7Vxucgh6DFnGkQqh A6afQjNmBikIFfvpIAw96vLscu6I8EmlLVXUYz8iF39mrP0tB3Mjautm0+BMcuzs zWSNVOyDfUFwZA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrledugdduuddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpemllhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpeduveegteeiieehfeduveevfeegjeeijedtveetkeeklefg gfelgeethedvudetgeenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 16 Aug 2021 13:13:58 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B59752A099B; Mon, 16 Aug 2021 13:13:55 -0400 (-04) Date: Mon, 16 Aug 2021 13:13:55 -0400 From: =?utf-8?Q?=C3=81lvaro?= Herrera To: Tom Lane Cc: Andres Freund , Kyotaro HORIGUCHI , yuzuko , Tomas Vondra , David Steele , Kyotaro Horiguchi , Justin Pryzby , Daniel Gustafsson , Amit Langote , Masahiko Sawada , Laurenz Albe , "pgsql-hackers@lists.postgresql.org" , Greg Stark Subject: Re: Autovacuum on partitioned table (autoanalyze) Message-ID: <202108161713.szuhvi5emfsf@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202108161700.d4eh6a7n2lki@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Another possible problem is that before the revert, we accept ALTER TABLE some_partitioned_table SET (autovacuum_enabled=on/off); (also autovacuum_analyze_scale_factor and autovacuum_analyze_threshold) but after the revert this is will throw a syntax error. What do people think we should do about that? 1. Do nothing. If somebody finds in that situation, they can use ALTER TABLE .. RESET ... to remove the settings. 2. Silently accept the option and do nothing. 3. Accept the option and throw a warning that it's a no-op. 4. Something else Opinions? -- Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/ Officer Krupke, what are we to do? Gee, officer Krupke, Krup you! (West Side Story, "Gee, Officer Krupke")