From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: David M <sircement@hotmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: MultiXactId xxxxxxxxx has not been created yet -- apparent wraparound
Date: Tue, 14 Jun 2016 13:31:50 -0400
Message-ID: <20160614173150.GA443784@alvherre.pgsql> (raw)
In-Reply-To: <SG2PR06MB0760098A111C88E31BD4D96FB3540@SG2PR06MB0760.apcprd06.prod.outlook.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
David M wrote:
> 4) What is the best course of action from here to fix the tables that we are having issues with ? (have already experimented with 'SELECT * FROM tablename FOR UPDATE' in a scratch system successfully allowing us to vacuum freeze the table)
This is your best bet. Using SELECT * FROM tablename FOR KEY SHARE
would likely have less impact in the concurrency of the system.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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: alvherre@2ndquadrant.com, sircement@hotmail.com
Subject: Re: MultiXactId xxxxxxxxx has not been created yet -- apparent wraparound
In-Reply-To: <20160614173150.GA443784@alvherre.pgsql>
* 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