Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-admin-owner+M47290=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1eAGwH-0000i2-IG
	for pgsql-admin@arkaria.postgresql.org; Thu, 02 Nov 2017 14:57:49 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-admin-owner+M47290=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1eAGwH-0008MR-4v
	for pgsql-admin@arkaria.postgresql.org; Thu, 02 Nov 2017 14:57:49 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1eAGwG-0008Ln-LQ
	for pgsql-admin@postgresql.org; Thu, 02 Nov 2017 14:57:48 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1eAGwD-0002bi-Jf
	for pgsql-admin@postgresql.org; Thu, 02 Nov 2017 14:57:48 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id vA2Evh1r001137;
	Thu, 2 Nov 2017 10:57:43 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Arjun Ranade <ranade@nodalexchange.com>
cc: pgsql-admin@postgresql.org
Subject: Re: Missing Chunk Error when doing a VACUUM FULL operation - DB
 Corruption?
In-reply-to: 
 <CANrrCRwrXQaxJRCtw0i8Kn3wcV_9EA+np=oBmsSfvjH1ieisXw@mail.gmail.com>
References: 
 <CANrrCRwH9ZnW+XtOxozEUPqWuHrfNNqDw9K3H69k513i7-YryQ@mail.gmail.com>
 <13631.1509479942@sss.pgh.pa.us>
 <CANrrCRy-qdDMX=a=xQsC9bbv36kD5biKUK3RgpNxUO9M-VfcTA@mail.gmail.com>
 <23996.1509486974@sss.pgh.pa.us>
 <CANrrCRyd81iKsjpjVpptBG+jzLxHt8rfWk9oj-tRDh7Agfbp8A@mail.gmail.com>
 <29089.1509487959@sss.pgh.pa.us>
 <CANrrCRxcFdXQvae7vrtWttHtXbVmB8yoYEt+2DhfADqm1fvb-g@mail.gmail.com>
 <CANrrCRy1_mu7A31Tas+-oKWcYK4kpNK8wTFW7VWVq+5yj2uApQ@mail.gmail.com>
 <19336.1509589417@sss.pgh.pa.us>
 <CANrrCRxzFYtJLmZSkpUVFh_2ZUcGnsO2nh3Cg78t2OLQEwfzGg@mail.gmail.com>
 <CANrrCRwrXQaxJRCtw0i8Kn3wcV_9EA+np=oBmsSfvjH1ieisXw@mail.gmail.com>
Comments: In-reply-to Arjun Ranade <ranade@nodalexchange.com>
	message dated "Thu, 02 Nov 2017 10:52:23 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1135.1509634663.1@sss.pgh.pa.us>
Date: Thu, 02 Nov 2017 10:57:43 -0400
Message-ID: <1136.1509634663@sss.pgh.pa.us>
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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