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)
Check Out this Related Man Page
CLUSTERDB(1) PostgreSQL 9.2.7 Documentation CLUSTERDB(1)NAME
clusterdb - cluster a PostgreSQL database
SYNOPSIS
clusterdb [connection-option...] [--verbose | -v] [--table | -t table] [dbname]
clusterdb [connection-option...] [--verbose | -v] --all | -a
DESCRIPTION
clusterdb is a utility for reclustering tables in a PostgreSQL database. It finds tables that have previously been clustered, and clusters
them again on the same index that was last used. Tables that have never been clustered are not affected.
clusterdb is a wrapper around the SQL command CLUSTER(7). There is no effective difference between clustering databases via this utility
and via other methods for accessing the server.
OPTIONS
clusterdb accepts the following command-line arguments:
-a, --all
Cluster all databases.
[-d] dbname, [--dbname=]dbname
Specifies the name of the database to be clustered. If this is not specified and -a (or --all) is not used, the database name is read
from the environment variable PGDATABASE. If that is not set, the user name specified for the connection is used.
-e, --echo
Echo the commands that clusterdb generates and sends to the server.
-q, --quiet
Do not display progress messages.
-t table, --table=table
Cluster table only.
-v, --verbose
Print detailed information during processing.
-V, --version
Print the clusterdb version and exit.
-?, --help
Show help about clusterdb command line arguments, and exit.
clusterdb 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 clusterdb to prompt for a password before connecting to a database.
This option is never essential, since clusterdb will automatically prompt for a password if the server demands password authentication.
However, clusterdb 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.
--maintenance-db=dbname
Specifies the name of the database to connect to discover what other databases should be clustered. If not specified, the postgres
database will be used, and if that does not exist, template1 will be used.
ENVIRONMENT
PGDATABASE, PGHOST, PGPORT, PGUSER
Default connection parameters
This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see Section 31.14, "Environment
Variables", in the documentation).
DIAGNOSTICS
In case of difficulty, see CLUSTER(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 cluster the database test:
$ clusterdb test
To cluster a single table foo in a database named xyzzy:
$ clusterdb --table foo xyzzy
SEE ALSO CLUSTER(7)PostgreSQL 9.2.7 2014-02-17 CLUSTERDB(1)