Re: [HACKERS] renaming pg_resetxlog to pg_resetwal has broken pg_upgrade. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] renaming pg_resetxlog to pg_resetwal has broken pg_upgrade.
Date
Msg-id CAB7nPqRmNrGgMVAya-5qCcip8HTgfc+PnBu_-CZpuH7WVfkAHQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] renaming pg_resetxlog to pg_resetwal has broken pg_upgrade.  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: [HACKERS] renaming pg_resetxlog to pg_resetwal has broken pg_upgrade.  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Feb 15, 2017 at 3:55 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
> I thought people would object to checking the version number in two
> different places to make the same fundamental decision, and would want that
> refactored somehow.  But if you are OK with it, then I am.

The binary versions are checked only once, which does not with change
HEAD. With this patch it happens just earlier, which makes the most
sense now that we have a condition depending on the version of what is
installed.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Set of fixes for WAL consistency check facility
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] WAL consistency check facility