pg_upgradecluster(8) [debian man page]
PG_UPGRADECLUSTER(8) Debian PostgreSQL infrastructure PG_UPGRADECLUSTER(8) NAME
pg_upgradecluster - upgrade an existing PostgreSQL cluster to a new major version. SYNOPSIS
pg_upgradecluster [-v newversion] version name [newdatadir] 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 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). Please note that the old cluster is set to "manual" startup mode, in order to avoid inadvertently changing it; this means that it will not be started automatically on system boot, and you have to use pg_ctlcluster(8) to start/stop it. See section "STARTUP CONTROL" in pg_createcluster(8) for details. 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. Please note that this program cannot upgrade clusters which use tablespaces. If you use those, you have to upgrade manually. OPTIONS
-v newversion Set the version to upgrade to (default: latest available). --logfile filel Set a custom log file path for the upgraded database cluster. --locale=locale Set the default locale for the upgraded database cluster. If this option is not specified, the locale is inherited from the old cluster. --lc-collate=locale --lc-ctype=locale --lc-messages=locale --lc-monetary=locale --lc-numeric=locale --lc-time=locale Like --locale, but only sets the locale in the specified category. 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 /etc/postgresql-common/pg_upgradecluster.d/. Script file names must consist entirely of upper and lower case letters, digits, underscores, and hyphens; in particular, dots (i. e. file extensions) are not allowed. 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. Please note that you should not create tables in this phase, since they will be overwritten by the dump/restore operation. 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> Debian 2012-10-08 PG_UPGRADECLUSTER(8)
Check Out this Related Man Page
INITDB(1) PostgreSQL Server Applications INITDB(1) NAME
initdb - create a new PostgreSQL database cluster SYNOPSIS
initdb [ option... ] [ --pgdata ] [ -D ] directory DESCRIPTION
initdb creates a new PostgreSQL database cluster. A database cluster is a collection of databases that are managed by a single server instance. Creating a database cluster consists of creating the directories in which the database data will live, generating the shared catalog tables (tables that belong to the whole cluster rather than to any particular database), and creating the template1 and postgres databases. When you later create a new database, everything in the template1 database is copied. (Therefore, anything installed in template1 is automati- cally copied into each database created later.) The postgres database is a default database meant for use by users, utilities and third party applications. Although initdb will attempt to create the specified data directory, it might not have permission if the parent directory of the desired data directory is root-owned. To initialize in such a setup, create an empty data directory as root, then use chown to assign ownership of that directory to the database user account, then su to become the database user to run initdb. initdb must be run as the user that will own the server process, because the server needs to have access to the files and directories that initdb creates. Since the server cannot be run as root, you must not run initdb as root either. (It will in fact refuse to do so.) initdb initializes the database cluster's default locale and character set encoding. The character set encoding, collation order (LC_COL- LATE) and character set classes (LC_CTYPE, e.g. upper, lower, digit) can be set separately for a database when it is created. initdb deter- mines those settings for the template1 database, which will serve as the default for all other databases. To alter the default collation order or character set classes, use the --lc-collate and --lc-ctype options. Collation orders other than C or POSIX also have a performance penalty. For these reasons it is important to choose the right locale when running initdb. The remaining locale categories can be changed later when the server is started. You can also use --locale to set the default for all locale categories, including collation order and character set classes. All server locale values (lc_*) can be displayed via SHOW ALL. More details can be found in in the documentation. To alter the default encoding, use the --encoding. More details can be found in in the documentation. OPTIONS
-A authmethod --auth=authmethod This option specifies the authentication method for local users used in pg_hba.conf. Do not use trust unless you trust all local users on your system. Trust is the default for ease of installation. -D directory --pgdata=directory This option specifies the directory where the database cluster should be stored. This is the only information required by initdb, but you can avoid writing it by setting the PGDATA environment variable, which can be convenient since the database server (post- gres) can find the database directory later by the same variable. -E encoding --encoding=encoding Selects the encoding of the template database. This will also be the default encoding of any database you create later, unless you override it there. The default is derived from the locale, or SQL_ASCII if that does not work. The character sets supported by the PostgreSQL server are described in in the documentation. --locale=locale Sets the default locale for the database cluster. If this option is not specified, the locale is inherited from the environment that initdb runs in. Locale support is described in in the documentation. --lc-collate=locale --lc-ctype=locale --lc-messages=locale --lc-monetary=locale --lc-numeric=locale --lc-time=locale Like --locale, but only sets the locale in the specified category. -X directory --xlogdir=directory This option specifies the directory where the transaction log should be stored. -U username --username=username Selects the user name of the database superuser. This defaults to the name of the effective user running initdb. It is really not important what the superuser's name is, but one might choose to keep the customary name postgres, even if the operating system user's name is different. -W --pwprompt Makes initdb prompt for a password to give the database superuser. If you don't plan on using password authentication, this is not important. Otherwise you won't be able to use password authentication until you have a password set up. --pwfile=filename Makes initdb read the database superuser's password from a file. The first line of the file is taken as the password. Other, less commonly used, parameters are also available: -d --debug Print debugging output from the bootstrap backend and a few other messages of lesser interest for the general public. The bootstrap backend is the program initdb uses to create the catalog tables. This option generates a tremendous amount of extremely boring out- put. -L directory Specifies where initdb should find its input files to initialize the database cluster. This is normally not necessary. You will be told if you need to specify their location explicitly. -n --noclean By default, when initdb determines that an error prevented it from completely creating the database cluster, it removes any files it might have created before discovering that it cannot finish the job. This option inhibits tidying-up and is thus useful for debug- ging. ENVIRONMENT
PGDATA Specifies the directory where the database cluster is to be stored; can be overridden using the -D option. This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see in the documentation). SEE ALSO
postgres(1) Application 2010-05-14 INITDB(1)