Re: ShmemAlloc errors - Mailing list pgsql-general

From Tom Lane
Subject Re: ShmemAlloc errors
Date
Msg-id 11970.1066325621@sss.pgh.pa.us
Whole thread Raw
In response to ShmemAlloc errors  (Nick Burrett <nick@dsvr.net>)
Responses Re: ShmemAlloc errors  (Sean Chittenden <sean@chittenden.org>)
Re: ShmemAlloc errors  (Nick Burrett <nick@dsvr.net>)
List pgsql-general
Nick Burrett <nick@dsvr.net> writes:
> $ pg_dumpall >full.db
> pg_dump: WARNING:  ShmemAlloc: out of memory
> pg_dump: Attempt to lock table "vs_dfa554862ac" failed.  ERROR:
> LockAcquire: lock table 1 is out of memory
> pg_dumpall: pg_dump failed on bandwidth, exiting

Looks like you need to increase max_locks_per_transaction in postgresql.conf.
(You'll need to restart the postmaster to make this take effect.)

We don't normally hear of people needing that --- is there anything
unusual about the schema of this database?

            regards, tom lane

pgsql-general by date:

Previous
From: Joseph Shraibman
Date:
Subject: Re: ShmemAlloc errors
Next
From: Tom Lane
Date:
Subject: Re: problem with function to report how many records were changed