Re: vacuumlo issue - Mailing list pgsql-hackers

From Josh Kupershmidt
Subject Re: vacuumlo issue
Date
Msg-id CAK3UJRH7Z+WV64RAuKxqP3iqusQ7W=41nLmF_fz-V1T=7jBvLw@mail.gmail.com
Whole thread Raw
In response to Re: vacuumlo issue  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: vacuumlo issue  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Mar 20, 2012 at 7:53 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I'm not entirely convinced that that was a good idea.  However, so far
> as vacuumlo is concerned, the only reason this is a problem is that
> vacuumlo goes out of its way to do all the large-object deletions in a
> single transaction.  What's the point of that?  It'd be useful to batch
> them, probably, rather than commit each deletion individually.  But the
> objects being deleted are by assumption unreferenced, so I see no
> correctness argument why they should need to go away all at once.

I think you are asking for this option:
 -l LIMIT     stop after removing LIMIT large objects

which was added in b69f2e36402aaa.

Josh


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Regarding column reordering project for GSoc 2012
Next
From: Greg Stark
Date:
Subject: Re: Memory usage during sorting