From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Zhihong Yu <zyu@yugabyte.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: pgsql: autovacuum: handle analyze for partitioned tables
Date: Fri, 09 Apr 2021 22:52:05 -0400
Message-ID: <2260573.1618023125@sss.pgh.pa.us> (raw)
In-Reply-To: <20210409234728.4zibyifpytgrh2fu@alap3.anarazel.de>
References: <2027895.1617969225@sss.pgh.pa.us>
<20210409155430.GA9512@alvherre.pgsql>
<20210409234728.4zibyifpytgrh2fu@alap3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> On 2021-04-09 11:54:30 -0400, Alvaro Herrera wrote:
>> Pushed now, thanks.
> 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)
Yeah, looks like the same thing to me; it's the same line that was
crashing in the non-valgrind reports.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, alvherre@alvh.no-ip.org, zyu@yugabyte.com, pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: autovacuum: handle analyze for partitioned tables
In-Reply-To: <2260573.1618023125@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox