Hi
I was vacuuming, but as the owner of the database. When I do that there
are messages that should have clued me in, lke
NOTICE: Skipping pg_largeobject --- only table owner can VACUUM it
From now on I will vacuum as user postgres, but I wonder if there is a
need for individual users to be
HI
I am having trouble with a 7.1rc4 database filling up my disks. What I do
is put a large number of small large objects of seismic data into the
database in one process and use another process to unlink them after they
reach a certain age to form a buffer. The unlink seems to be working, and
Philip Crotwell [EMAIL PROTECTED] writes:
I poked around in the database directory and found a file named 16948 that
is 960Mb or almost all of the space on my partition.
That is pg_largeobject. Vacuuming should recover the lost space; are
you sure you've vacuumed it?
