Re: Autovacuum on partitioned table - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Autovacuum on partitioned table
Date
Msg-id 20200318014910.GA19400@alvherre.pgsql
Whole thread Raw
In response to Re: Autovacuum on partitioned table  (yuzuko <yuzukohosoya@gmail.com>)
Responses Re: Autovacuum on partitioned table  (yuzuko <yuzukohosoya@gmail.com>)
List pgsql-hackers
On 2020-Mar-18, yuzuko wrote:

> > I think if we analyze partition tree in order from leaf partitions
> > to root table, this problem can be fixed.
> > What do you think about it?
> 
> Attach the new patch fixes the above problem.

Thanks for the new version.

I'm confused about some error messages in the regression test when a
column is mentioned twice, that changed from mentioning the table named
in the vacuum command, to mentioning the first partition.  Is that
because you changed an lappend() to lcons()?  I think you do this so
that the counters accumulate for the topmost parent that will be
processed at the end.  I'm not sure I like that too much ... I think
that needs more thought.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: WIP: WAL prefetch (another approach)
Next
From: David Rowley
Date:
Subject: Re: [PATCH] Erase the distinctClause if the result is unique by definition