Postgres Pro
Downloads
Home   >   mailing lists

Re: [ADMIN] Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption? - Mailing list pgsql-admin

From Tom Lane
Subject Re: [ADMIN] Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?
Date
Msg-id 1136.1509634663@sss.pgh.pa.us
Whole thread Raw
In response to Re: [ADMIN] Missing Chunk Error when doing a VACUUM FULL operation -DB Corruption?  (Arjun Ranade <ranade@nodalexchange.com>)
Responses Re: [ADMIN] Missing Chunk Error when doing a VACUUM FULL operation -DB Corruption?  (Stephen Frost <sfrost@snowman.net>)
List pgsql-admin
Tree view 
Arjun Ranade <ranade@nodalexchange.com> writes:
> After dropping the replication slot, VACUUM FULL runs fine now and no
> longer reports the "oldest xmin is far in the past"

Excellent.  Maybe we should think about providing better tools to notice
"stuck" replication slots.

In the meantime, you probably realize this already, but if global xmin
has been stuck for months then you're going to have terrible bloat
everywhere.  Database-wide VACUUM FULL seems called for.
        regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

pgsql-admin by date:

Previous
From: Arjun Ranade
Date:
Subject: Re: [ADMIN] Missing Chunk Error when doing a VACUUM FULL operation -DB Corruption?
Next
From: Stephen Frost
Date:
Subject: Re: [ADMIN] Missing Chunk Error when doing a VACUUM FULL operation -DB Corruption?