Re: pg_upgrade resets timeline to 1

From: Noah Misch <noah(at)leadboat(dot)com>
To: Christoph Berg <myon(at)debian(dot)org>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Marco Nenciarini <mnencia(at)debian(dot)org>
Subject: Re: pg_upgrade resets timeline to 1
Date: 2015-05-29 00:59:11
Message-ID: 20150529005911.GB4121096@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 28, 2015 at 05:26:56PM +0200, Christoph Berg wrote:
> Re: Noah Misch 2015-05-28 <20150528150234(dot)GA4111886(at)tornado(dot)leadboat(dot)com>
> > To clarify for the archives, the 2015-05-16 changes did not revert to 9.3 and
> > earlier behavior. Rather, they standardized on the {9.0,9.1,9.2}-to-{9.3,9.4}
> > upgrade behavior, bringing that behavior to all supported branches and source
> > versions. Here is the history of timeline restoration in pg_upgrade:
>
> Ok, sorry for the noise then. It's not a regression, but I still think
> the behavior needs improvement, but this is indeed 9.6 material.

No, thank you for the report. It had strong signs of being a regression,
considering recent changes and the timing of your discovery.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2015-05-29 01:04:05 Re: [PATCH] readlink missing nul-termination in pg_rewind
Previous Message Peter Eisentraut 2015-05-29 00:51:01 Re: Patch to improve a few appendStringInfo* calls