Re: MultiXact member wraparound protections are disabled

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: "AnandKumar, Karthik" <Karthik(dot)AnandKumar(at)classmates(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: MultiXact member wraparound protections are disabled
Date: 2016-10-13 10:00:40
Message-ID: 20161013100040.ptmpurnflmsjjtv2@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

AnandKumar, Karthik wrote:
> root(at)site-db01a:/var/lib/pgsql/cmates/data # ls pg_multixact/members
> 0000 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B 000C 000D 000E 000F 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 001A 001B
> root(at)site-db01a:/var/lib/pgsql/cmates/data # ls pg_multixact/offsets
> 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B

> postgres(at)site-db01a:~ $ /usr/pgsql-9.4/bin/pg_controldata /var/lib/pgsql/cmates/data

> Latest checkpoint's NextMultiXactId: 784503
> Latest checkpoint's NextMultiOffset: 1445264
> Latest checkpoint's oldestMultiXid: 1
> Latest checkpoint's oldestMulti's DB: 16457

This looks perfectly normal, except that the pg_multixact/offsets/0000
file is gone. oldestMultiXid is 1 so I don't see how could have the
file gotten removed. Has this been upgraded recently from a previous
9.3 or 9.4 version? There have been bugs in this area but they've been
fixed now for some time.

The 0000 file could have been removed manually, perhaps?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message AnandKumar, Karthik 2016-10-13 10:44:06 Re: MultiXact member wraparound protections are disabled
Previous Message Andreas Joseph Krogh 2016-10-13 08:14:08 pg_upgrade not able to cope with pg_largeobject being in a different tablespace