From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pre-version pg_upgrade syntax check |
Date: | 2020-02-10 23:45:32 |
Message-ID: | 3698bbe2-6082-acda-58a0-2f8c15fee1b2@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/10/20 3:40 PM, Rich Shepard wrote:
> On Mon, 10 Feb 2020, Rich Shepard wrote:
>
>> Good advice; I'll do that.
>
> Huh! Not what I expected:
>
> postgres(at)salmo:~$ pg_upgrade -c -b /usr/lib64/postgresql/11/bin/ -B
> /usr/lib64/postgresql/12/bin/ -d /var/lib/pgsql/11/data -D
> /var/lib/pgsql/12/data/
>
> (All on one line; wrapped by alpine.)
>
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions Old cluster data and binary directories are
> from different major versions.
> Failure, exiting
>
> Well, of course they're from different major versions, that's why I'm
> running pg_upgrade. What did I do incorrectly?
What it is saying is -b and -d are pointing at binary and data
directories that are incompatible. You need to make sure that:
/usr/lib64/postgresql/11/bin/
and
/var/lib/pgsql/11/data
are actually pointing at 11 instances of binaries and data respectively.
>
> Rich
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2020-02-11 00:07:43 | Re: Pre-version pg_upgrade syntax check |
Previous Message | Rich Shepard | 2020-02-10 23:40:22 | Re: Pre-version pg_upgrade syntax check |