Re: renaming pg_resetxlog to pg_resetwal has broken pg_upgrade.

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(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 18:55:50
Message-ID: CAMkU=1w5rNZ9z2=C=zD=qPG+eJ9W6fL2NeX9xrWmM2OtLsFdCg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 13, 2017 at 6:19 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:

> On Tue, Feb 14, 2017 at 9:09 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> > check for "/usr/local/pgsql9_6/bin/pg_resetwal" failed: No such file or
> > directory
> >
> > This looks somewhat complicated to fix. Should check_bin_dir test the
> old
> > cluster version, and make a deterministic check based on that? Or just
> > check for either spelling, and stash the successful result somewhere?
>
> The fix does not seem that complicated to me. get_bin_version() just
> needs pg_ctl to be present, so we could move that in check_bin_dir()
> after looking if pg_ctl is in a valid state, and reuse the version of
> bin_version to see if the binary version is post-10 or not. Then the
> decision making just depends on this value. Please see the patch
> attached, this is passing 9.6->10 and check-world.
>

That fixes it for me.

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.

Cheers,

Jeff

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2017-02-14 19:05:20 Re: PATCH: two slab-like memory allocators
Previous Message Robert Haas 2017-02-14 18:41:33 Re: gitlab post-mortem: pg_basebackup waiting for checkpoint