| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "MUHAMMAD ASIF *EXTERN*" <anaeem(dot)it(at)hotmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: vacuumlo issue |
| Date: | 2012-03-20 14:53:37 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C207A2B200@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 memory
>
> HINT: You might need to increase max_locks_per_transaction.
This is not a question for the hackers list.
vacuumlo handles all deletes in a single transaction, so
max_locks_per_transaction can be exhausted.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-03-20 15:21:36 | Re: Regarding column reordering project for GSoc 2012 |
| Previous Message | Tom Lane | 2012-03-20 14:53:07 | Re: vacuumlo issue |