Re: pgsql: autovacuum: handle analyze for partitioned tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgsql: autovacuum: handle analyze for partitioned tables
Date
Msg-id 2260573.1618023125@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: autovacuum: handle analyze for partitioned tables  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Avoid unnecessary table open/close for TRUNCATE foo, foo, foo; kind of commands
Next
From: Noah Misch
Date:
Subject: Re: pgsql: Move tablespace path re-creation from the makefiles to pg_regres