table of contents
VACUUMLO(1) | PostgreSQL 16.1 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
--limit=limit
-n
--dry-run
-v
--verbose
-V
--version
-?
--help
vacuumlo also accepts the following command-line arguments for connection parameters:
-h host
--host=host
-p port
--port=port
-U username
--username=username
-w
--no-password
-W
--password
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.
ENVIRONMENT¶
PGHOST
PGPORT
PGUSER
This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see Section 34.15).
The environment variable PG_COLOR specifies whether to use color in diagnostic messages. Possible values are always, auto and never.
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>
2023 | PostgreSQL 16.1 |