Re: renaming pg_resetxlog to pg_resetwal has broken pg_upgrade.

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: renaming pg_resetxlog to pg_resetwal has broken pg_upgrade.
Date: 2017-02-14 22:13:42
Message-ID: CAB7nPqRmNrGgMVAya-5qCcip8HTgfc+PnBu_-CZpuH7WVfkAHQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 15, 2017 at 3:55 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-02-14 22:16:37 Re: WAL consistency check facility
Previous Message Michael Paquier 2017-02-14 22:08:03 Re: Set of fixes for WAL consistency check facility