vacuumlo(1) [centos man page]

VACUUMLO(1)						  PostgreSQL 9.2.7 Documentation					       VACUUMLO(1)

NAME

       vacuumlo - remove orphaned large objects from a PostgreSQL database

SYNOPSIS

       vacuumlo [option...] dbname...

DESCRIPTION

       vacuumlo is a simple utility program that will remove any "orphaned" large objects from a PostgreSQL database. An orphaned large object
       (LO) is considered to be any LO whose OID does not appear in any oid or lo data column of the database.

       If you use this, you may also be interested in the lo_manage trigger in the lo module.  lo_manage is useful to try to avoid creating
       orphaned LOs in the first place.

       All databases named on the command line are processed.

OPTIONS

       vacuumlo accepts the following command-line arguments:

       -l limit
	   Remove no more than limit large objects per transaction (default 1000). Since the server acquires a lock per LO removed, removing too
	   many LOs in one transaction risks exceeding max_locks_per_transaction. Set the limit to zero if you want all removals done in a single
	   transaction.

       -n
	   Don't remove anything, just show what would be done.

       -v
	   Write a lot of progress messages.

       -V, --version
	   Print the vacuumlo version and exit.

       -?, --help
	   Show help about vacuumlo command line arguments, and exit.

       vacuumlo also accepts the following command-line arguments for connection parameters:

       -h hostname
	   Database server's host.

       -p port
	   Database server's port.

       -U username
	   User name to connect as.

       -w, --no-password
	   Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as a
	   .pgpass file, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to enter a
	   password.

       -W
	   Force vacuumlo to prompt for a password before connecting to a database.

	   This option is never essential, since vacuumlo will automatically prompt for a password if the server demands password authentication.
	   However, vacuumlo will waste a connection attempt finding out that the server wants a password. In some cases it is worth typing -W to
	   avoid the extra connection attempt.

NOTES

       vacuumlo works by the following method: First, vacuumlo builds a temporary table which contains all of the OIDs of the large objects in the
       selected database. It then scans through all columns in the database that are of type oid or lo, and removes matching entries from the
       temporary table. (Note: Only types with these names are considered; in particular, domains over them are not considered.) The remaining
       entries in the temporary table identify orphaned LOs. These are removed.

AUTHOR

       Peter Mount <peter@retep.org.uk>

PostgreSQL 9.2.7						    2014-02-17							       VACUUMLO(1)

DROPDB(1)						  PostgreSQL Client Applications						 DROPDB(1)

NAME

       dropdb - remove a PostgreSQL database

SYNOPSIS

       dropdb [ option... ]  dbname

DESCRIPTION

       dropdb destroys an existing PostgreSQL database.  The user who executes this command must be a database superuser or the owner of the data-
       base.

       dropdb is a wrapper around the SQL command DROP DATABASE [drop_database(7)].  There is no effective difference between  dropping  databases
       via this utility and via other methods for accessing the server.

OPTIONS

       dropdb accepts the following command-line arguments:

       dbname Specifies the name of the database to be removed.

       -e

       --echo Echo the commands that dropdb generates and sends to the server.

       -i

       --interactive
	      Issues a verification prompt before doing anything destructive.

       dropdb also accepts the following command-line arguments for connection parameters:

       -h host

       --host host
	      Specifies the host name of the machine on which the server is running. If the value begins with a slash, it is used as the directory
	      for the Unix domain socket.

       -p port

       --port port
	      Specifies the TCP port or local Unix domain socket file extension on which the server is listening for connections.

       -U username

       --username username
	      User name to connect as.

       -w

       --no-password
	      Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as
	      a  .pgpass  file,  the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to
	      enter a password.

       -W

       --password
	      Force dropdb to prompt for a password before connecting to a database.

	      This option is never essential, since dropdb will automatically prompt for a password if the server demands password authentication.
	      However,	dropdb	will waste a connection attempt finding out that the server wants a password.  In some cases it is worth typing -W
	      to avoid the extra connection attempt.

ENVIRONMENT

       PGHOST

       PGPORT

       PGUSER Default connection parameters

       This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see in the documentation).

DIAGNOSTICS

       In case of difficulty, see DROP DATABASE [drop_database(7)] and psql(1) for discussions of potential  problems  and  error  messages.   The
       database  server  must  be  running at the targeted host. Also, any default connection settings and environment variables used by the libpq
       front-end library will apply.

EXAMPLES

       To destroy the database demo on the default database server:

       $ dropdb demo

       To destroy the database demo using the server on host eden, port 5000, with verification and a peek at the underlying command:

       $ dropdb -p 5000 -h eden -i -e demo
       Database "demo" will be permanently deleted.
       Are you sure? (y/n) y
       DROP DATABASE demo;

SEE ALSO

       createdb(1), DROP DATABASE [drop_database(7)]

Application							    2010-05-14								 DROPDB(1)