Re: BUG #10911: pg_upgrade appears to lose the transaction id epoch

From: Greg Stark <stark(at)mit(dot)edu>
To: gregburek(at)heroku(dot)com
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #10911: pg_upgrade appears to lose the transaction id epoch
Date: 2014-07-08 23:46:24
Message-ID: CAM-w4HMdS16opwKtRR1AdMPiK61w0Qw3v+VNrdyBcMFxaH75Ag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jul 8, 2014 at 10:17 PM, <gregburek(at)heroku(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mitu Verma 2014-07-09 07:01:09 Re: BUG #10888: application is getting hanged in the poll() function of libpq.so.
Previous Message Bruce Momjian 2014-07-08 22:48:28 Re: BUG #10911: pg_upgrade appears to lose the transaction id epoch