Re: pg_upgrade resets timeline to 1 - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: pg_upgrade resets timeline to 1
Date
Msg-id 20150528152656.GG22629@msg.df7cb.de
Whole thread Raw
In response to Re: pg_upgrade resets timeline to 1  (Noah Misch <noah@leadboat.com>)
Responses Re: pg_upgrade resets timeline to 1  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
Re: Noah Misch 2015-05-28 <20150528150234.GA4111886@tornado.leadboat.com>
> On Thu, May 28, 2015 at 10:20:58AM -0400, Bruce Momjian wrote:
> > On Thu, May 28, 2015 at 08:47:07AM +0100, Simon Riggs wrote:
> > > What we should be saying is that the last timeline doesn't need a history file.
> > > Then no change is needed here.
> > 
> > Yes, that would make a lot more sense than what we have now, but this
> > had to be backpatched, so reverting to the 9.3 and earlier behavior
> > seemed logical.
> 
> 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.

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: proleakproof vs opr_sanity test
Next
From: Tom Lane
Date:
Subject: Re: WIP: Enhanced ALTER OPERATOR