NAME
pg_upgradecluster - upgrade a new PostgreSQL cluster to a new major version.
SYNOPSIS
pg_upgradecluster [-v newversion] version name [data dir]
DESCRIPTION
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 cluster.
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 be removed. After upgrade, please verify that the new cluster
indeed works as expected; if so, you should remove the old cluster with
pg_dropcluster(8).
HOOK SCRIPTS
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
CW/etc/postgresql-common/pg_upgradecluster.d/. Scripts in that
directory will be called with the following arguments:
<old version> <cluster name> <new version> <phase>
Phases:
"init"
A virgin cluster of version new version has been created, i. e. this new
cluster will already have template1, but no user databases.
"finish"
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.
SEE ALSO
pg_createcluster(8), pg_dropcluster(8), pg_lsclusters(1), pg_wrapper(1)
AUTHOR
Martin Pitt <mpitt@debian.org>
