Re: [JDBC] unlink large objects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Crotwell <crotwell(at)seis(dot)sc(dot)edu>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [JDBC] unlink large objects
Date: 2001-06-09 16:59:58
Message-ID: 10019.992105998@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Philip Crotwell <crotwell(at)seis(dot)sc(dot)edu> writes:
> 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 able to vacuum large obects by themselves.

Good point. More generally, it seems like it might be a good idea to
allow the owner of an individual database to vacuum all the system
catalogs in it, even if he's not the superuser. Comments anyone?

> Also, when the disk is nearly full, I am seeing the database crash while
> trying to vacuum.

From WAL log overflow, no doubt. If you look in the pgsql-patches
archives from the last week or two, there is a patch to alleviate the
growth of the log.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message D'Arcy J.M. Cain 2001-06-09 17:47:39 Re: ERROR: Memory exhausted in AllocSetAlloc(909324558)
Previous Message Tom Lane 2001-06-09 16:53:28 Re: Various silliness in heap_getnext and related routines

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bruce Momjian 2001-06-09 20:32:46 Re: Re: [JDBC] unlink large objects
Previous Message Philip Crotwell 2001-06-09 14:13:26 Re: unlink large objects