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

From: Greg Stark <stark(at)mit(dot)edu>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: gregburek <gregburek(at)heroku(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #10911: pg_upgrade appears to lose the transaction id epoch
Date: 2014-07-09 10:54:27
Message-ID: CAM-w4HNu6BmU8UjvKQeb=--Dto0ERJoXtfwmcMf8-VPfN1Dtpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I think all that's required is to read the epoch at the same time as
the xid and set it at the same time.

I tested this only using the harness so that's a 9.4->9.4 pg_upgrade.
It would be worth testing on older versions but I don't see any
changes to pg_controldata that would be relevant since 8.2 when the
epoch was added.

Attachment Content-Type Size
pg_upgrade_epoch.diff text/plain 3.1 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Haribabu Kommi 2014-07-09 13:21:30 Re: [BUGS] BUG #9652: inet types don't support min/max
Previous Message Mitu Verma 2014-07-09 07:01:09 Re: BUG #10888: application is getting hanged in the poll() function of libpq.so.