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 1lV13q-0002c3-51 for pgsql-hackers@arkaria.postgresql.org; Sat, 10 Apr 2021 00:01:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lV13o-0006CX-TA for pgsql-hackers@arkaria.postgresql.org; Sat, 10 Apr 2021 00:01:12 +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 1lV13o-0006CQ-Lq for pgsql-hackers@lists.postgresql.org; Sat, 10 Apr 2021 00:01:12 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lV13l-00063T-UI for pgsql-hackers@lists.postgresql.org; Sat, 10 Apr 2021 00:01:11 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 64E5C5C00A2; Fri, 9 Apr 2021 20:01:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 09 Apr 2021 20:01:08 -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=9h/TBYMf/R5Hl2UcB8LXl9Y2NVHsahHKS2arwMnWsJw=; b=FB/mYsnP c/n8TN7gTSxBOzV2fgiiKC8m2gelPw/BMRlCc1oDM5kEl0canZPGp5KUwlzO1rTT 5gBYoBy4Omha4WdBOG4a8jUYMQkX8P0ASur8HcqA3Nbc2aY6qw3hQEwsnbK/YX7n 8+HRnx7MxtodpcEc+qEgaQA2my9QPjzRCFnVIpXfr2+hKZE84P4LwjkMvCvN9Jv8 4Y1KhM/UsetVF+LR7TafBu3IefBepsqllMGlMwRRmng6zI2SZXKjNj7p+ni1m6VS 0Zmn2xq1IakjcqaGXnh2dNONhFT8LhKTcnWMQARK7d9tXzXSUDaT/OLXdZsjbBbH /In9HRfl5ipwcQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudekvddgvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjfgesthekredttderudenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepveejjeekjeejieevueduvdefffeihfffgfelhefgueeg jeehuddvfeekiefhffdtnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenuc fkphepudeltddrleehrdduledrleehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.95]) by mail.messagingengine.com (Postfix) with ESMTPA id A664F24005E; Fri, 9 Apr 2021 20:01:07 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id E6B912A092C; Fri, 9 Apr 2021 20:01:04 -0400 (-04) Date: Fri, 9 Apr 2021 20:01:04 -0400 From: Alvaro Herrera To: Andres Freund Cc: Tom Lane , Zhihong Yu , PostgreSQL Developers Subject: Re: pgsql: autovacuum: handle analyze for partitioned tables Message-ID: <20210410000104.GA7025@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210409234728.4zibyifpytgrh2fu@alap3.anarazel.de> 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 Hello On 2021-Apr-09, Andres Freund wrote: > I assume this is also the likely explanation for / fix for: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2021-04-08%2016%3A03%3A03 > > ==3500389== VALGRINDERROR-BEGIN > ==3500389== Invalid read of size 8 > ==3500389== at 0x4EC4B8: relation_needs_vacanalyze (autovacuum.c:3237) > ==3500389== by 0x4EE0AF: do_autovacuum (autovacuum.c:2168) > ==3500389== by 0x4EEEA8: AutoVacWorkerMain (autovacuum.c:1715) > ==3500389== by 0x4EEF7F: StartAutoVacWorker (autovacuum.c:1500) > ==3500389== by 0x4FD2E4: StartAutovacuumWorker (postmaster.c:5539) Hmm, I didn't try to reproduce this, but yeah it sounds quite likely that it's the same issue -- line 3237 is the GETSTRUCT call where the other one was crashing, which is now gone. Thanks for pointing it out, -- Álvaro Herrera Valdivia, Chile