Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eAH4m-0001fG-Tq for pgsql-admin@arkaria.postgresql.org; Thu, 02 Nov 2017 15:06:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1eAH4m-0000jo-Ac for pgsql-admin@arkaria.postgresql.org; Thu, 02 Nov 2017 15:06:36 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eAH4l-0000je-OS for pgsql-admin@postgresql.org; Thu, 02 Nov 2017 15:06:35 +0000 Received: from static-96-255-250-162.washdc.fios.verizon.net ([96.255.250.162] helo=tamriel.snowman.net) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eAH4e-0001XG-J8 for pgsql-admin@postgresql.org; Thu, 02 Nov 2017 15:06:34 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 949385F797; Thu, 2 Nov 2017 11:06:27 -0400 (EDT) Date: Thu, 2 Nov 2017 11:06:27 -0400 From: Stephen Frost To: Tom Lane Cc: Arjun Ranade , pgsql-admin@postgresql.org Subject: Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption? Message-ID: <20171102150627.GJ4628@tamriel.snowman.net> References: <23996.1509486974@sss.pgh.pa.us> <29089.1509487959@sss.pgh.pa.us> <19336.1509589417@sss.pgh.pa.us> <1136.1509634663@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ax1DT/G4360cstoB" Content-Disposition: inline In-Reply-To: <1136.1509634663@sss.pgh.pa.us> User-Agent: Mutt/1.5.21 (2010-09-15) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --Ax1DT/G4360cstoB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Tom, Arjun, * Tom Lane (tgl@sss.pgh.pa.us) wrote: > Arjun Ranade writes: > > After dropping the replication slot, VACUUM FULL runs fine now and no > > longer reports the "oldest xmin is far in the past" >=20 > 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 --Ax1DT/G4360cstoB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJZ+zRzAAoJEO1sijiDR2RVdJgQAJPjXc3YiGsraTRzI38SQazC 4XzHylksOP09uNeNBkPI8K+dZVMDyDFOvzBCBrkSbYYMS1/rbQlsZGvjyl4eGdfD EAxsbpuBCMvNqahqxsk48qcq87rjK6dre47cZOOr5bp84NhrA+wwmPC1MJw6pez9 lAmIWzUm6gmMDkll37Kj5hfl6VKh8OIHZStjPsUC0PLJ80yzWl3k00hvUPm0sBxr UwJuQR94dxOm2inS6rKQe2wGsSlwfB4GNO+0KjkSreUNL6gD8iNQ7pxCIrbS3wcM G6wC1w8l/pS9jzFHGsE2vJj3V6KlTyUAfJEjtn61Rtk5IxbtR5AmhsX3+5ixYC0F JQ/9g3T4CYnS+zK0knFYqmkj5GvQwqSm8dong5JCE1U/SmI+3jOVYhHC6v0faqru wYP1Aqp3PUkzZVivNFhsj3BtAqSTkoG+tq4VGWC5VbwkoiT3NOTwXe/N3tgu6ZkA URAzMLFtDVVMGR3XGKSU2QfTM03GL8nzwnKu70S0kczCM4Od+z1um7gPLpohL3Dm eR3n1Oc2rhB3qFMVsJ5abLVrS3fUjmjRm5tvcBEhElFmTjIjhG9/bwunkJsuc/C9 eoUy4prz8cdyAdqq9GU3BtlQ9EM51IVXeqsRxsZ5yGexWBwjbkx2d2NxWr6F1BJk VySqh95BnAw/UviLXh// =J/ps -----END PGP SIGNATURE----- --Ax1DT/G4360cstoB--