Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pg_wrapper(1) [debian man page]

PG_WRAPPER(1)						 Debian PostgreSQL infrastructure					     PG_WRAPPER(1)

pg_wrapper - wrapper for PostgreSQL client commands SYNOPSIS
client-program [--cluster version/cluster] [...] (client-program: psql, createdb, dropuser, and all other client programs installed in /usr/lib/postgresql/version/bin). DESCRIPTION
This program is run only as a link to names which correspond to PostgreSQL programs in /usr/lib/postgresql/version/bin. It determines the configured cluster and database for the user and calls the appropriate version of the desired program to connect to that cluster and database, supplying any specified options to that command. The target cluster is selected by the following means, in descending order of precedence: 1. explicit specification with the --host option 2. explicit specification with the --cluster option 3. if the PGHOST environment variable is set, no further cluster selection is performed. The default PostgreSQL version and port number (from the command line, the environment variable PGPORT, or default 5432) will be used. 4. explicit specification with the PGCLUSTER environment variable 5. matching entry in ~/.postgresqlrc (see postgresqlrc(5)), if that file exists 6. matching entry in /etc/postgresql-common/user_clusters (see user_clusters(5)), if that file exists 7. If only one local cluster exists, that one will be selected. 8. If several local clusters exist, the one listening on the default port 5432 will be selected. If none of these rules match, pg_wrapper aborts with an error. OPTIONS
--cluster version/cluster cluster is either the name of a local cluster, or takes the form host:port for a remote cluster. If port is left empty (i. e. you just specify host:), it defaults to 5432. ENVIRONMENT
PGCLUSTER If $PGCLUSTER is set, its value (of the form version/cluster) specifies the desired cluster, similar to the --cluster option. However, if --cluster is specified, it overrides the value of $PGCLUSTER. PG_CLUSTER_CONF_ROOT This specifies an alternative base directory for cluster configurations. This is usually /etc/postgresql/, but for testing/development purposes you can change this to point to e. g. your home directory, so that you can use the postgresql-common tools without root privileges. FILES
/etc/postgresql-common/user_clusters stores the default cluster and database for users and groups as set by the administrators. $HOME/.postgresqlrc stores defaults set by the user himself. SEE ALSO
user_clusters(5), postgresqlrc(5) AUTHOR
Martin Pitt <> Debian 2013-01-04 PG_WRAPPER(1)

Check Out this Related Man Page

cmdeleteconf(1m)														  cmdeleteconf(1m)

cmdeleteconf - Delete either the cluster or the package configuration SYNOPSIS
cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...] DESCRIPTION
cmdeleteconf deletes either the entire cluster configuration, including all its packages, or only the specified package configuration. If neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all its packages. If the local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration. If only the package_name is specified, the configuration of package_name in the local cluster is deleted. If both cluster_name and pack- age_name are specified, the package must be configured in the cluster_name, and only the package package_name will be deleted. cmdelete- conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the con- figuration version. The local cluster is the cluster that the node running the cmdeleteconf command belongs to. Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can delete the configuration. To delete the cluster configuration, halt the cluster first. To delete a package configuration you must halt the package first, but you do not need to halt the cluster (it may remain up or be brought down). To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete all packages with STORAGE_GROUP defined. While deleting the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration. In this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster. If the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config- uration before doing any other Serviceguard command. Options cmdeleteconf supports the following options: -f Force the deletion of either the cluster configuration or the package configuration. -v Verbose output will be displayed. -c cluster_name Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster. -p package_name Name of an existing package to delete from the cluster. The package must be halted already. There should not be any packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only). RETURN VALUE
Upon completion, cmdeleteconf returns one of the following values: 0 Successful completion. 1 Command failed. EXAMPLES
The high availability environment contains the cluster, clusterA , and a package, pkg1. To delete package pkg1 in clusterA, do the following: cmdeleteconf -f -c clusterA -p pkg1 To delete the cluster clusterA and all its packages, do the following: cmdeleteconf -f -c clusterA AUTHOR
cmdeleteconf was developed by HP. SEE ALSO
cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m). Requires Optional Serviceguard Software cmdeleteconf(1m)
Man Page

Featured Tech Videos