Re: [HACKERS] vacuumlo issue

2012-03-20 Thread Tom Lane
Robert Haas writes: > On Tue, Mar 20, 2012 at 11:50 AM, Tom Lane wrote: >> I see that patch has not made it to any released versions yet. >> Is it too late to rethink the design? I propose (a) redefining it >> as committing after every N objects, and (b) having a limit of 1000 >> or so objects b

Re: [HACKERS] vacuumlo issue

2012-03-20 Thread MUHAMMAD ASIF
> > I think you are asking for this option: > > -l LIMIT stop after removing LIMIT large objects > > which was added in b69f2e36402aaa. Thank you for informing about -l option in 9.2. Can I build/use this contrib with older pg versions i.e. pg 9.1 ? . Thanks. > Uh, no, actually that flag s

Re: [HACKERS] vacuumlo issue

2012-03-20 Thread Robert Haas
On Tue, Mar 20, 2012 at 11:50 AM, Tom Lane wrote: > Josh Kupershmidt writes: >> On Tue, Mar 20, 2012 at 7:53 AM, Tom Lane 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

Re: [HACKERS] vacuumlo issue

2012-03-20 Thread Tom Lane
Josh Kupershmidt writes: > On Tue, Mar 20, 2012 at 7:53 AM, Tom Lane 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 >>

Re: [HACKERS] vacuumlo issue

2012-03-20 Thread Josh Kupershmidt
On Tue, Mar 20, 2012 at 7:53 AM, Tom Lane 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 th

Re: [HACKERS] vacuumlo issue

2012-03-20 Thread Albe Laurenz
MUHAMMAD ASIF wrote: > We have noticed the following issue with vacuumlo database that have millions > of record > in pg_largeobject i.e. [...] > ~/work/pg/postgresql-9.1.2/inst$ bin/vacuumlo vacuumlo_test > > WARNING:  out of shared memory > Failed to remove lo 36726: ERROR:  out of shared mem

Re: [HACKERS] vacuumlo issue

2012-03-20 Thread Tom Lane
MUHAMMAD ASIF writes: > We have noticed the following issue with vacuumlo database that have millions > of record in pg_largeobject i.e. >WARNING: out of shared memoryFailed to remove lo 155987:ERROR: out > of shared memory HINT: You might need to increase > max_locks_per_transacti

Re: [HACKERS] vacuumlo issue

2012-03-20 Thread MUHAMMAD ASIF
I have reformatted the mail, sorry for inconvenience. Thanks. We have noticed the following issue with vacuumlo database that have millions of record in pg_largeobject i.e. WARNING: out of shared memory Failed to remove lo 155987:ERROR: out of shared memory HINT: You m

[HACKERS] vacuumlo issue

2012-03-20 Thread MUHAMMAD ASIF
Hi, We have noticed the following issue with vacuumlo database that have millions of record in pg_largeobject i.e.    WARNING:  out of shared memoryFailed to remove lo 155987:    ERROR:  out of shared memory   HINT:  You might need to increase max_locks_per_transaction. Why do we need to increa