Thread: Upgrading error

chris navarroza <canavarroza.work@gmail.com> writes:
> bash-4.4$ /usr/pgsql-14/bin/pg_upgrade
> --old-datadir=/home/dmartuser/pgdata/data/
> --new-datadir=/home/dmartuser/pgdata/data/ --old-bindir=/usr/pgsql-12/bin/
> --new-bindir=/usr/pgsql-14/bin/ --check --verbose
> Running in verbose mode
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions
> This utility can only upgrade to PostgreSQL version 14.

You cannot use the same directory as --old-datadir and --new-datadir.
I think pg_upgrade is unhappy because what it sees in PG_VERSION in
the --new-datadir isn't v14 ... but I wonder if we shouldn't be
checking for this mistake more directly.

Anyway, the right way to proceed is to use v14's initdb to create
a new directory at, say, /home/dmartuser/pgdata/data-14
and then pg_upgrade to that.  Afterwards you can rename the old
data directory out of the way and move the new one to
/home/dmartuser/pgdata/data, if you like.

            regards, tom lane

chris navarroza <canavarroza.work@gmail.com> writes:
> could not connect to source postmaster started with the command:
> "/usr/pgsql-12/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
> "/home/dmartuser/pgdata/data" -o "-p 50432 -b -c
> config_file=/var/lib/pgsql/12/data/postgresql.conf -c listen_addresses=''
> -c unix_socket_permissions=0700 -c unix_socket_directories='/tmp'" start
> Failure, exiting

Did you look into the postmaster log (pg_upgrade_server.log, here)
to see what it thought about the problem?  I'm guessing there's
something that kept it from starting, but there's no evidence
offered here about what.

            regards, tom lane