Provided by: postgresql-common_87_all
pg_upgradecluster - upgrade an existing PostgreSQL cluster to a new
pg_upgradecluster [-v newversion] version name [newdatadir]
pg_upgradecluster upgrades an existing PostgreSQL server cluster (i. e.
a collection of databases served by a postmaster instance) to a new
version specified by newversion (default: latest available version).
The configuration files of the old version are copied to the new
The cluster of the old version will be configured to use a previously
unused port since the upgraded one will use the original port. The old
cluster is not automatically removed. After upgrading, please verify
that the new cluster indeed works as expected; if so, you should remove
the old cluster with pg_dropcluster(8).
The newdatadir argument can be used to specify a non-default data
directory of the upgraded cluster. It is passed to pg_createcluster. If
not specified, this defaults to /var/lib/postgresql/version/name.
Some PostgreSQL extensions like PostGIS need metadata in auxiliary
tables which must not be upgraded from the old version, but rather
initialized for the new version before copying the table data. For this
purpose, extensions (as well as administrators, of course) can drop
upgrade hook scripts into /etc/postgresql-common/pg_upgradecluster.d/.
Scripts in that directory will be called with the following arguments:
<old version> <cluster name> <new version> <phase>
A virgin cluster of version new version has been created, i. e.
this new cluster will already have template1, but no user
All data from the old version cluster has been dumped/reloaded into
the new one. The old cluster still exists.
The scripts are called as the user who owns the database.
pg_createcluster(8), pg_dropcluster(8), pg_lsclusters(1), pg_wrapper(1)
Martin Pitt <firstname.lastname@example.org>