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

From Gavin Flower
Subject Re: pg_upgrade resets timeline to 1
Date
Msg-id 5567BF53.1070608@archidevsys.co.nz
Whole thread Raw
In response to Re: pg_upgrade resets timeline to 1  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On 29/05/15 12:59, Noah Misch wrote:
> On Thu, May 28, 2015 at 05:26:56PM +0200, Christoph Berg wrote:
>> Re: Noah Misch 2015-05-28 <20150528150234.GA4111886@tornado.leadboat.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.
>
>From my experience, I would far rather a user raise concerns that are 
important to them, and find there is no real problem, than users not 
raising things and a serious bug or system shorting coming go unnoticed.

This is a major concern of mine, for example: in my current project, 
where users were NOT raising problems in a timely manner, caused 
unnecessary work rather later in the project than I would have liked!

So not just for PostgreSQL, but in general if a user has concerns, 
please raise them!!!


Cheers,
Gavin



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH] readlink missing nul-termination in pg_rewind
Next
From: Andrew Dunstan
Date:
Subject: Re: RFC: Remove contrib entirely