Tom Lane 3bf25a2a16 Back-patch contrib/vacuumlo's new -l (limit) option into 9.0 and 9.1. ...

Since 9.0, removing lots of large objects in a single transaction risks
exceeding max_locks_per_transaction, because we merged large object removal
into the generic object-drop mechanism, which takes out an exclusive lock
on each object to be dropped.  This creates a hazard for contrib/vacuumlo,
which has historically tried to drop all unreferenced large objects in one
transaction.  There doesn't seem to be any correctness requirement to do it
that way, though; we only need to drop enough large objects per transaction
to amortize the commit costs.

To prevent a regression from pre-9.0 releases wherein vacuumlo worked just
fine, back-patch commits b69f2e3640 and
64c604898e, which break vacuumlo's deletions
into multiple transactions with a user-controllable upper limit on the
number of objects dropped per transaction.

Tim Lewis, Robert Haas, Tom Lane

2012-03-21 13:05:05 -04:00

..

.gitignore

Convert cvsignore to gitignore, and add .gitignore for build targets.

2010-09-22 12:57:06 +02:00

Makefile

Add PGFILEDESC description to Makefiles for all /contrib executables.

2010-05-12 11:33:10 +00:00

vacuumlo.c

Back-patch contrib/vacuumlo's new -l (limit) option into 9.0 and 9.1.

2012-03-21 13:05:05 -04:00