Re: Question about DROP TABLE - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Question about DROP TABLE
Date
Msg-id 20160112113721.propayaclisblniy@alap3.anarazel.de
Whole thread Raw
In response to Re: Question about DROP TABLE  (Michal Novotny <michal.novotny@trustport.com>)
Responses Re: Question about DROP TABLE
Re: Question about DROP TABLE
List pgsql-hackers
Hi,

On 2016-01-12 12:17:01 +0100, Michal Novotny wrote:
> thanks a lot for your reply. Unfortunately I've found out most it didn't
> really start DROP TABLE yet and it's locked on autovacuum running for
> the table and even if I kill the process it's autostarting again and again.

Start the DROP TABLE and *then* cancel the autovacuum session. That
should work.

> Is there any way how to do the DROP TABLE and bypass/disable autovacuum
> entirely? Please note the "autovacuum = off" is set in the config file
> (postgresql.conf).

That actually is likely to have caused the problem. Every
autovacuum_freeze_max_age tables need to be vacuumed - otherwise the
data can't be interpreted correctly anymore at some point. That's called
'anti-wraparound vacuum". It's started even if you disabled autovacuum,
to prevent database corruption.

If you disable autovacuum, you really should start vacuums in some other
way.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Rushabh Lathia
Date:
Subject: Re: Optimization for updating foreign tables in Postgres FDW
Next
From: Thom Brown
Date:
Subject: Re: Odd behavior in foreign table modification (Was: Re: Optimization for updating foreign tables in Postgres FDW)