summaryrefslogtreecommitdiff
path: root/contrib/vacuumlo
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-06-23 00:06:37 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-06-23 00:06:37 +0000
commit5b0c9d3603b027e022b8a0ebd4c492469a5d1633 (patch)
treea6cf50fa8f63616d4889c869814ed205f6216faa /contrib/vacuumlo
parentd20763dbee7cdf8a700bf6bdd120b3913a3b99f4 (diff)
downloadpostgresql-5b0c9d3603b027e022b8a0ebd4c492469a5d1633.tar.gz
Cleanup the contrib/lo module: there is no need anymore to implement
a physically separate type. Defining 'lo' as a domain over OID works just fine and is more efficient. Improve documentation and fix up the test script. (Would like to turn test script into a proper regression test, but right now its output is not constant because of numeric OIDs; plus it makes Unix-specific assumptions about files it can import.)
Diffstat (limited to 'contrib/vacuumlo')
-rw-r--r--contrib/vacuumlo/README.vacuumlo6
1 files changed, 5 insertions, 1 deletions
diff --git a/contrib/vacuumlo/README.vacuumlo b/contrib/vacuumlo/README.vacuumlo
index b72ecf18e0..560649a654 100644
--- a/contrib/vacuumlo/README.vacuumlo
+++ b/contrib/vacuumlo/README.vacuumlo
@@ -1,9 +1,13 @@
-$PostgreSQL: pgsql/contrib/vacuumlo/README.vacuumlo,v 1.4 2003/11/29 19:51:36 pgsql Exp $
+$PostgreSQL: pgsql/contrib/vacuumlo/README.vacuumlo,v 1.5 2005/06/23 00:06:37 tgl Exp $
This is a simple utility that will remove any orphaned large objects out of a
PostgreSQL database. An orphaned LO is considered to be any LO whose OID
does not appear in any OID data column of the database.
+If you use this, you may also be interested in the lo_manage trigger in
+contrib/lo. lo_manage is useful to try to avoid creating orphaned LOs
+in the first place.
+
Compiling
--------