Re: MultiXactId xxxxxxxxx has not been created yet -- apparent wraparound

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: David M <sircement(at)hotmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: MultiXactId xxxxxxxxx has not been created yet -- apparent wraparound
Date: 2016-06-14 17:31:50
Message-ID: 20160614173150.GA443784@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Łukasz Brodziak 2016-06-16 08:19:10 Adding same column to several tables.
Previous Message Rupesh Choudhary 2016-06-14 16:27:20