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

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

On Thu, Jun 04, 2015 at 05:29:51PM -0400, Robert Haas wrote:
> Here's a new version with some more fixes and improvements:

I read through this version and found nothing to change. I encourage other
hackers to study the patch, though. The surrounding code is challenging.

> With this version, I'm able to see that when you start up a
> 9.3.latest+this patch with a cluster that has a bogus value of 1 in
> relminmxid, datminmxid, and the control file, autovacuum vacuums
> everything in sight, all the values get set back to the right thing,
> and the next checkpoint enables the member-wraparound guards.

Nice.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Munro 2015-06-05 10:51:53 Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
Previous Message William Dunn 2015-06-05 04:53:07 Re: Database designpattern - product feature

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2015-06-05 06:50:31 Re: [CORE] Restore-reliability mode
Previous Message Amit Kapila 2015-06-05 05:21:28 Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file