Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1

From: Steve Kehlet <steve(dot)kehlet(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Forums postgresql <pgsql-general(at)postgresql(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
Date: 2015-06-12 23:27:12
Message-ID: CA+bfosGfrjYDCK7wfDJki6ymNwQnhrTAsAWj21zVy6PquDHsXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Just wanted to report that I rolled back my VM to where it was with 9.4.2
installed and it wouldn't start. I installed 9.4.4 and now it starts up
just fine:

> 2015-06-12 16:05:58 PDT [6453]: [1-1] LOG: database system was shut down
at 2015-05-27 13:12:55 PDT
> 2015-06-12 16:05:58 PDT [6453]: [2-1] LOG: MultiXact member wraparound
protections are disabled because oldest checkpointed MultiXact 1 does not
exist on disk
> 2015-06-12 16:05:58 PDT [6457]: [1-1] LOG: autovacuum launcher started
> 2015-06-12 16:05:58 PDT [6452]: [1-1] LOG: database system is ready to
accept connections
> done
> server started

And this is showing up in my serverlog periodically as the emergency
autovacuums are running:

> 2015-06-12 16:13:44 PDT [6454]: [1-1] LOG: MultiXact member wraparound
protections are disabled because oldest checkpointed MultiXact 1 does not
exist on disk

**Thank you Robert and all involved for the resolution to this.**

> With the fixes introduced in this release, such a situation will result
in immediate emergency autovacuuming until a correct oldestMultiXid value
can be determined

Okay, I notice these vacuums are of the "to prevent wraparound" type (like
VACUUM FREEZE), that do hold locks preventing ALTER TABLEs and such. Good
to know, we'll plan our software updates accordingly.

Is there any risk until these autovacuums finish?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mephysto 2015-06-13 08:58:32 Re: FW: PostgreSQL and iptables
Previous Message Bill Moran 2015-06-12 22:56:14 Re: Momentary Delay

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2015-06-12 23:31:09 Re: Further issues with jsonb semantics, documentation
Previous Message Sehrope Sarkuni 2015-06-12 22:36:05 Re: Entities created in one query not available in another in extended protocol