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 1la07x-0001zQ-Cn for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Apr 2021 18:02:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1la07w-0005Zb-4m for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Apr 2021 18:02:04 +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 1la07v-0005ZU-KO for pgsql-hackers@lists.postgresql.org; Fri, 23 Apr 2021 18:02:03 +0000 Received: from mail-il1-x12a.google.com ([2607:f8b0:4864:20::12a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1la07n-00012D-QV for pgsql-hackers@lists.postgresql.org; Fri, 23 Apr 2021 18:02:02 +0000 Received: by mail-il1-x12a.google.com with SMTP id r5so1201868ilb.2 for ; Fri, 23 Apr 2021 11:01:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=wADszPNRwF/T9oEKI5kCE9wXGWl3gNcL+FNikWyX72w=; b=Rp86bFwwD0XsPQAs6ot2W4ea0JN/v7FDMS1tbyF1haXKYaad355YVbW4NGkIW/8yDk /FQ9cB7lZN3+SL2YIkpiunrb4J1lp9hr5WIntxWQwL7EdNOwaBxkfm/oS4LtwiodigAW //YX4QL8rz78kjTxeInCiJWYoNhX9uvQnM6vnUFq2GPaQkcF/gqOEAPQ4oOgp1R8lUZh zOqN7I6GvtUFs8X4uiBJHNI71DKMuZ9/5wMwrLfAQzeMjkh2x6UMJRgAco7Rtr5FZniU Y/xBkqPByktsH8DGF0cKmAthD+Ztm008S7wZgu8yc6qGEhKJIwKUvQde0W/tJKqKltIC W5ZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=wADszPNRwF/T9oEKI5kCE9wXGWl3gNcL+FNikWyX72w=; b=rR2+6lmBVDor95hZXjrxk56RwyG5EUSbFpUCzzTybS85oK/nzlgenwkmw9ztg/DpXV 4l7rSlOy7PlBj4AdlV2dA5DHWYDUQWcaiwPQsWttW5iohoom4TfQyagewkuFXfG0TJdq Qm+AhOexPuXU3AYC9FK45FYgHlHDdI5+eE/gVwgcVrBKg87CkUdftnnPtMQ7+KWRW+hH ZhH3gdCSzyOceAAxqvPeOpFq+dl6OSAuvzwdWj/FqBuBTHnXUzzcF935nmgDBsKX6Nuh D/2UPim/L/bka88XnI+JF7R8lXzI+mBoTGZFtsO1Nf7sn/ShopRPtsa0iB0085vlv0tz I+wA== X-Gm-Message-State: AOAM533uO1HEpdCvYL5zNL0euznADJu1XdQEgcqqN8Uku8axFDVJZA1w n4b9N+3v0I75wgsxxG777VrnJQ== X-Google-Smtp-Source: ABdhPJzm43M4waWy6X81HFh/Xu2otqVJLlQDLzzqwzWi2PVJlAko/RBQ3WgSgRGBvqM3ERy9FcnYtQ== X-Received: by 2002:a92:d143:: with SMTP id t3mr4229471ilg.241.1619200915039; Fri, 23 Apr 2021 11:01:55 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id v26sm3011848ioh.42.2021.04.23.11.01.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Apr 2021 11:01:54 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id AA168801559; Fri, 23 Apr 2021 13:01:52 -0500 (CDT) Date: Fri, 23 Apr 2021 13:01:52 -0500 From: Justin Pryzby To: Alvaro Herrera Cc: Robert Haas , Tom Lane , Zhihong Yu , pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: autovacuum: handle analyze for partitioned tables Message-ID: <20210423180152.GA17270@telsasoft.com> References: <20210421230649.GA19244@alvherre.pgsql> <20210422174346.GE7256@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210422174346.GE7256@telsasoft.com> 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, Apr 22, 2021 at 12:43:46PM -0500, Justin Pryzby wrote: > Maybe the behavior should be documented, though. Actually, I thought the > pre-existing (non)behavior of autoanalyze would've been documented, and we'd > now update that. All I can find is this: > > https://www.postgresql.org/docs/current/sql-analyze.html > |The autovacuum daemon, however, will only consider inserts or updates on the > |parent table itself when deciding whether to trigger an automatic analyze for > |that table > > I think that should probably have been written down somewhere other than for > the manual ANALYZE command, but in any case it seems to be outdated now. Starting with this