Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Arjun Ranade <ranade(at)nodalexchange(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?
Date: 2017-11-02 14:57:43
Message-ID: 1136.1509634663@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Arjun Ranade <ranade(at)nodalexchange(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Stephen Frost 2017-11-02 15:06:27 Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?
Previous Message Arjun Ranade 2017-11-02 14:52:23 Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?