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 1lT8zu-0007fO-CA for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Apr 2021 20:05:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lT8zt-0005JB-AA for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Apr 2021 20:05:25 +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 1lT8zs-0005J4-9i for pgsql-hackers@lists.postgresql.org; Sun, 04 Apr 2021 20:05:25 +0000 Received: from new3-smtp.messagingengine.com ([66.111.4.229]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lT8zo-0005BE-Gv for pgsql-hackers@lists.postgresql.org; Sun, 04 Apr 2021 20:05:23 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.nyi.internal (Postfix) with ESMTP id E3CF65804F6; Sun, 4 Apr 2021 16:05:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 04 Apr 2021 16:05:18 -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= fm2; bh=s6dGR+kz6Rif+/ol80lJwGbt4Qh5McYabmwAQZ/oMuI=; b=FtrD3f0e FbuW6qHjZuMBjwLnTD7gaiLzrdIC7WuZJIVSWtiOLrxHLcTAn9WuBetItsmmXn2q vqlgrYG0ixTG4khDXnH7lezQtsUR1UfqT2+u1u2wHzGmcuesMQc/axnRA6Zj+MJ1 QsNvxPX26kEHfqylik/WpkvzS9OK1nP330MG1TMQH/RVjNYb0X6li13AC1p4u6gV phBYW24o2rOVzc44KU+YJFtZE9EMUJvpLPE1GBBwpi2DZ2csp2uNSihsAJHcNZf0 r9sOTpGrXD6xO74qCVRIn+nEEPQhKE4jRjIlEbhZ3/MtlngzZeohgl7Zi9XmJxRZ GYV4EaNnFFpi2g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudejtddgudegiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkgggtugfgjggfsehtkeertddtredunecuhfhrohhmpeetlhhv rghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorh hgqeenucggtffrrghtthgvrhhnpeeufffhjeeiueeuffegvddukeegledtveeivdeiueef ieeivefgteehueefteehvdenucfkphepudeltddrleehrdduledrleehnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegr lhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.95]) by mail.messagingengine.com (Postfix) with ESMTPA id 624C9240057; Sun, 4 Apr 2021 16:05:17 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id A1DFA2A0D53; Sun, 4 Apr 2021 16:05:14 -0400 (-04) Date: Sun, 4 Apr 2021 16:05:14 -0400 From: Alvaro Herrera To: Tomas Vondra Cc: yuzuko , David Steele , Kyotaro Horiguchi , Justin Pryzby , Daniel Gustafsson , Amit Langote , Masahiko Sawada , Laurenz Albe , PostgreSQL Hackers , Greg Stark Subject: Re: Autovacuum on partitioned table (autoanalyze) Message-ID: <20210404200514.GA5220@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <73dc10a0-cc6a-5d12-7f0f-e7410fa76d9c@enterprisedb.com> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Apr-04, Tomas Vondra wrote: > 1) I still don't understand why inheritance and declarative partitioning > are treated differently. Seems unnecessary nad surprising, but maybe > there's a good reason? I suppose the rationale is that for inheritance we have always done it that way -- similar things have been done that way for inheritance historically, to avoid messing with long-standing behavior. We have done that in a bunch of places -- DDL behavior, FKs, etc. Maybe in this case it's not justified. It *will* change behavior, in the sense that we are going to capture stats that have never been captured before. That might or might not affect query plans for designs using regular inheritance. But it seems reasonable to think that those changes will be for the good; and if it does break plans for some people and they want to revert to the original behavior, they can just set autovacuum_enabled to off for the parent tables. So, I agree that we should enable this new feature for inheritance parents too. I can't comment on the other issues. I hope to give this a closer look tomorrow my time; with luck Hosoya-san will have commented by then. -- Álvaro Herrera 39°49'30"S 73°17'W "La rebeldía es la virtud original del hombre" (Arthur Schopenhauer)