Re: DROP TABLE and autovacuum - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: DROP TABLE and autovacuum
Date
Msg-id 20070614141209.GG5105@alvh.no-ip.org
Whole thread Raw
In response to Re: DROP TABLE and autovacuum  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: DROP TABLE and autovacuum  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-hackers
Alvaro Herrera wrote:
> ITAGAKI Takahiro wrote:

> > Hmm, how about canceling only the cases of DROP TABLE, TRUNCATE and CLUSTER.
> > We will obviously not need the table after the commands. Other commands,
> > VACUUM (FULL), ANALYZE, CREATE INDEX (CONCURRENTLY), REINDEX and LOCK TABLE
> > still conflict with autovacuum, but I'll leave it as-is in the meantime.
> 
> Well, all of DROP TABLE, TRUNCATE and CLUSTER seem safe -- and also,
> they will advance the table's relfrozenxid.  No objection there.

Something worth considering, though unrelated to the topic at hand: what
happens with the table stats after CLUSTER?  Should we cause an ANALYZE
afterwards?  We could end up running with outdated statistics.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Can autovac try to lock multiple tables at once?
Next
From: Greg Smith
Date:
Subject: Re: Sorted writes in checkpoint