1VACUUMLO(1)             PostgreSQL 9.2.24 Documentation            VACUUMLO(1)
2
3
4

NAME

6       vacuumlo - remove orphaned large objects from a PostgreSQL database
7

SYNOPSIS

9       vacuumlo [option...] dbname...
10

DESCRIPTION

12       vacuumlo is a simple utility program that will remove any “orphaned”
13       large objects from a PostgreSQL database. An orphaned large object (LO)
14       is considered to be any LO whose OID does not appear in any oid or lo
15       data column of the database.
16
17       If you use this, you may also be interested in the lo_manage trigger in
18       the lo module.  lo_manage is useful to try to avoid creating orphaned
19       LOs in the first place.
20
21       All databases named on the command line are processed.
22

OPTIONS

24       vacuumlo accepts the following command-line arguments:
25
26       -l limit
27           Remove no more than limit large objects per transaction (default
28           1000). Since the server acquires a lock per LO removed, removing
29           too many LOs in one transaction risks exceeding
30           max_locks_per_transaction. Set the limit to zero if you want all
31           removals done in a single transaction.
32
33       -n
34           Don't remove anything, just show what would be done.
35
36       -v
37           Write a lot of progress messages.
38
39       -V, --version
40           Print the vacuumlo version and exit.
41
42       -?, --help
43           Show help about vacuumlo command line arguments, and exit.
44
45       vacuumlo also accepts the following command-line arguments for
46       connection parameters:
47
48       -h hostname
49           Database server's host.
50
51       -p port
52           Database server's port.
53
54       -U username
55           User name to connect as.
56
57       -w, --no-password
58           Never issue a password prompt. If the server requires password
59           authentication and a password is not available by other means such
60           as a .pgpass file, the connection attempt will fail. This option
61           can be useful in batch jobs and scripts where no user is present to
62           enter a password.
63
64       -W
65           Force vacuumlo to prompt for a password before connecting to a
66           database.
67
68           This option is never essential, since vacuumlo will automatically
69           prompt for a password if the server demands password
70           authentication. However, vacuumlo will waste a connection attempt
71           finding out that the server wants a password. In some cases it is
72           worth typing -W to avoid the extra connection attempt.
73

NOTES

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

AUTHOR

85       Peter Mount <peter@retep.org.uk>
86
87
88
89PostgreSQL 9.2.24                 2017-11-06                       VACUUMLO(1)
Impressum