From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
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-28 15:26:56 |
Message-ID: | 20150528152656.GG22629@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: Noah Misch 2015-05-28 <20150528150234(dot)GA4111886(at)tornado(dot)leadboat(dot)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(at)df7cb(dot)de | http://www.df7cb.de/
From | Date | Subject | |
---|---|---|---|
Next Message | Abhijit Menon-Sen | 2015-05-28 15:43:48 | [PATCH] readlink missing nul-termination in pg_rewind |
Previous Message | Tom Lane | 2015-05-28 15:09:10 | proleakproof vs opr_sanity test |