Re: Question about DB VACUUM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cjwhite(at)cisco(dot)com
Cc: "'Robert Treat'" <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Question about DB VACUUM
Date: 2003-10-07 04:24:19
Message-ID: 20681.1065500659@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Chris White \(cjwhite\)" <cjwhite(at)cisco(dot)com> writes:
> Okay now I understand what is going on. I have a second thread which is
> being used to read these objects out of the database to present to the
> user, and because large objects can only be accessed in a transaction
> mode I have not closed the transaction on this thread. Should I do a
> commit or rollback to terminate the transaction, once I have closed the
> large object, even though I have not done any modifications to the large
> objects?

Yes, if you need to reclaim the space from recently-deleted large
objects. Under ordinary scenarios I'd not think that you have to be
real tense about this. However, if your reader thread was in the habit
of holding open the same transaction for hours or days, that would be
a Bad Thing ...

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ganesan Kanavathy 2003-10-07 08:42:46 Checking Postgres Database
Previous Message Chris White (cjwhite) 2003-10-07 04:20:43 Re: Question about DB VACUUM