Hi,
I'm trying to upgrade a 8.4 DB (from Debian packages on Debian Lenny)
to 9.3 (installation from source) with pg_upgrade. But he doesn't
launch the new postmaster. Any ideas?
postgres@SPV:~$ /opt/nova/current/nova/parts/pg93/bin/pg_upgrade -b
/usr/lib/postgresql/8.4/bin -B /opt/nova/current/nova/parts/pg93/bin/
-d /srv/postgresql/8.4/main/ -D /srv/postgresql/9.3/main --check
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is a superuser ok
Checking for prepared transactions ok
Checking for reg* system OID user data types ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for large objects ok
Checking for presence of required libraries ok
Checking database user is a superuser ok
Checking for prepared transactions ok
*Clusters are compatible*
postgres@SPV:/tmp$ /opt/nova/current/nova/parts/pg93/bin/pg_upgrade -b
/usr/lib/postgresql/8.4/bin -B /opt/nova/current/nova/parts/pg93/bin
-d /srv/postgresql/8.4/main/ -D /srv/postgresql/9.3/main
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is a superuser ok
Checking for prepared transactions ok
Checking for reg* system OID user data types ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for large objects ok
Creating dump of global objects
*failure*
Consult the last few lines of "pg_upgrade_utility.log" for
the probable cause of the failure.
Failure, exiting
postgres@SPV:/tmp$ ls
pg_upgrade_internal.log pg_upgrade_server.log
pg_upgrade_utility.log upgrade_successful
postgres@SPV:/tmp$ cat pg_upgrade_internal.log
-----------------------------------------------------------------
pg_upgrade run on Thu Feb 13 23:13:54 2014
-----------------------------------------------------------------
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is a superuser ok
Checking for prepared transactions ok
Checking for reg* system OID user data types ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for large objects ok
Creating dump of global objects
*failure*
Consult the last few lines of "pg_upgrade_utility.log" for
the probable cause of the failure.
postgres@SPV:/tmp$ cat pg_upgrade_server.log
-----------------------------------------------------------------
pg_upgrade run on Thu Feb 13 23:13:54 2014
-----------------------------------------------------------------
command: "/usr/lib/postgresql/8.4/bin/pg_ctl" -w -l
"pg_upgrade_server.log" -D "/srv/postgresql/8.4/main/" -o "-p 50432 -c
autovacuum=off -c autovacuum_freeze_max_age=2000000000 -c
listen_addresses='' -c unix_socket_permissions=0700" start >>
"pg_upgrade_server.log" 2>&1
waiting for server to start.... done
server started
command: "/usr/lib/postgresql/8.4/bin/pg_ctl" -w -D
"/srv/postgresql/8.4/main/" -o "" -m fast stop >>
"pg_upgrade_server.log" 2>&1
waiting for server to shut down.... done
server stopped
postgres@SPV:/tmp$ cat pg_upgrade_utility.log
-----------------------------------------------------------------
pg_upgrade run on Thu Feb 13 23:13:54 2014
-----------------------------------------------------------------
command: "/opt/nova/current/nova/parts/pg93/bin/pg_dumpall" --port
50432 --username "postgres" --schema-only --globals-only
--quote-all-identifiers --binary-upgrade -f
pg_upgrade_dump_globals.sql >> "pg_upgrade_utility.log" 2>&1
pg_dumpall: could not connect to database "template1": could not
connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.50432"?
--
Sebastien Douche <sdouche@xxxxxxxxx>
Twitter: @sdouche / G+: +sdouche
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
