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

From Alvaro Herrera
Subject Re: pgsql: autovacuum: handle analyze for partitioned tables
Date
Msg-id 20210421230649.GA19244@alvherre.pgsql
Whole thread Raw
In response to Re: pgsql: autovacuum: handle analyze for partitioned tables  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pgsql: autovacuum: handle analyze for partitioned tables  (yuzuko <yuzukohosoya@gmail.com>)
Re: pgsql: autovacuum: handle analyze for partitioned tables  (Justin Pryzby <pryzby@telsasoft.com>)
Re: pgsql: autovacuum: handle analyze for partitioned tables  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2021-Apr-09, Robert Haas wrote:

> Does this need to worry about new partitions getting attached to a
> partitioned table, or old ones getting detached? (Maybe it does
> already, not sure.)

I was pinged because this is listed as an open item.  I don't think it
is one.  Handling ATTACH/DETACH/DROP is important for overall
consistency, of course, so we should do it eventually, but the fact that
autovacuum runs analyze *at all* for partitioned tables is an enormous
step forward from it not doing so.  I think we should treat ATTACH/
DETACH/DROP handling as a further feature to be added in a future
release, not an open item to be fixed in the current one.

Now, if somebody sees a very trivial way to handle it, let's discuss it,
but *I* don't see it.

-- 
Álvaro Herrera       Valdivia, Chile
"You're _really_ hosed if the person doing the hiring doesn't understand
relational systems: you end up with a whole raft of programmers, none of
whom has had a Date with the clue stick."              (Andrew Sullivan)



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: autovacuum: handle analyze for partitioned tables
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: when the startup process doesn't