Hi,
I have upgraded the postgresql-common and postgresql-client-common :
ii postgresql-9.1 9.1.14-1.pgdg70+1 amd64 object-relational SQL
database, version 9.1 server
ii postgresql-9.3 9.3.5-1.pgdg70+1 amd64 object-relational SQL
database, version 9.3 server
ii postgresql-client-9.1 9.1.14-1.pgdg70+1
amd64 front-end programs for PostgreSQL 9.1
ii postgresql-client-9.3 9.3.5-1.pgdg70+1
amd64 front-end programs for PostgreSQL 9.3
ii postgresql-client-common 163
all manager for multiple PostgreSQL client versions
iF postgresql-common 163
all PostgreSQL database-cluster manager
But I got the same error :
root@p2tstl2mondbm:/var/lib# pg_upgradecluster 9.1 main --method=upgrade
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...
Stopping old cluster...
Creating new cluster 9.3/main ...
config /etc/postgresql/9.3/main
data /var/lib/postgresql/9.3/main
locale C
Flags of /var/lib/postgresql/9.3/main set as ---------------C
port 5433
Error: could not create symlink /var/lib/postgresql/9.1/main/pg_ident.conf
Re-enabling connections to the old cluster...
Error during cluster dumping, removing new cluster
pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
exist
Is server running?
Error: could not reload old cluster, please do that manually
root@p2tstl2mondbm:/var/lib#
Thanks a lot for your help
Matthieu
Le 6/12/14 14:56, Peter Eisentraut a écrit :
On 12/6/14 3:14 AM, Matthieu Lejeune wrote:
Creating new cluster 9.3/main ...
config /etc/postgresql/9.3/main
data /var/lib/postgresql/9.3/main
locale C
port 5433
Error: could not symlink configuration file
Error during cluster dumping, removing new cluster
pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
exist
Is server running?
Error: could not reload old cluster, please do that manually
root@p2tstl2mondbm:/var/lib/postgresql#
It's trying to symlink the configuration files into the data directory
before calling pg_upgrade. I think it complains that the symlinks are
already there, from a previous runs. Could could try manually removing
them from the data directory.
This was apparently fixed in postgresql-common version 155 (see
https://github.com/petere/postgresql-common/commit/323253ed95ec00faaf042217749e3f4c7e3617b3).
If you want to, you could also try to get an updated version from
apt.postgresql.org.
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
