pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Arjun Ranade <ranade@nodalexchange.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?
Date: Thu, 2 Nov 2017 11:06:27 -0400
Message-ID: <20171102150627.GJ4628@tamriel.snowman.net> (raw)
In-Reply-To: <1136.1509634663@sss.pgh.pa.us>
References: <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>
	<1136.1509634663@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Tom, Arjun,

* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> 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.

+1

> 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.

This, really, is also a lesson in "monitor your distance to transaction
wrap-around"..  You really should know something is up a lot sooner than
the warnings from PG showing up in the logs.

Thanks!

Stephen

Attachments:

  signature.asc (application/pgp-signature, 818B) download

view thread (15+ messages)  latest in thread

Message-ID: <20171102150627.GJ4628@tamriel.snowman.net>
Permalink:  ../20171102150627.GJ4628@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20171102150627.GJ4628@tamriel.snowman.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: sfrost@snowman.net, tgl@sss.pgh.pa.us, ranade@nodalexchange.com
  Subject: Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?
  In-Reply-To: <20171102150627.GJ4628@tamriel.snowman.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox