Re: BUG #10911: pg_upgrade appears to lose the transaction id epoch - Mailing list pgsql-bugs

From Greg Stark
Subject Re: BUG #10911: pg_upgrade appears to lose the transaction id epoch
Date
Msg-id CAM-w4HMdS16opwKtRR1AdMPiK61w0Qw3v+VNrdyBcMFxaH75Ag@mail.gmail.com
Whole thread Raw
In response to BUG #10911: pg_upgrade appears to lose the transaction id epoch  (gregburek@heroku.com)
List pgsql-bugs
On Tue, Jul 8, 2014 at 10:17 PM,  <gregburek@heroku.com> wrote:
> Looking at pg_control before the upgrade:
> $ pg_controldata /database/ | grep -i nextxid
> Latest checkpoint's NextXID:          15/1905728256
>
> After the upgrade:
> $ pg_controldata /database/ | grep -i nextxid
> Latest checkpoint's NextXID:          0/1905029398

You could just do "pg_resetxlog -e 15" to work around the problem
(after a clean shutdown).

--
greg

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #10911: pg_upgrade appears to lose the transaction id epoch
Next
From: Mitu Verma
Date:
Subject: Re: BUG #10888: application is getting hanged in the poll() function of libpq.so.