From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
Cc: | Sergey Burladyan <eshkinkot(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade and epoch |
Date: | 2014-09-05 23:19:57 |
Message-ID: | 20140905231957.GE26717@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 2, 2014 at 10:38:55PM -0700, Sergey Konoplev wrote:
> On Tue, Sep 2, 2014 at 7:59 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > On Wed, Apr 23, 2014 at 12:41:41PM -0700, Sergey Konoplev wrote:
> >> On Wed, Apr 23, 2014 at 5:26 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> > Sergey, are you seeing a problem only because you are
> >> > interacting with other systems that didn't reset their epoch?
> >>
> >> I faced this after upgrading clusters with PgQ Skytools3 installed
> >> only. They didn't interact with any other systems.
> >
> > I have developed the attached patch which causes pg_upgrade to preserve
> > the transaction epoch. I plan to apply this for PG 9.5.
>
> That is a great news. Thank you, Bruce.
Patch applied.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2014-09-05 23:22:48 | Re: Display of timestamp in pg_dump custom format |
Previous Message | Andrew Dunstan | 2014-09-05 23:18:20 | Re: PL/pgSQL 2 |