| From: | Sean Chittenden <sean(at)chittenden(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Nick Burrett <nick(at)dsvr(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ShmemAlloc errors |
| Date: | 2003-10-16 20:36:45 |
| Message-ID: | 20031016203645.GA25509@perrin.nxad.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > $ 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?
I've bumped into this a few times way back when... any chance the
error message could be improved to include a hint to increase
max_locks_per_transaction? It took a bit of time digging to figure
out that was a valid solution. -sc
--
Sean Chittenden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edwin Quijada | 2003-10-16 20:48:29 | Re: is possible to read oracle tables from PostgresSQL |
| Previous Message | Jordan S. Jones | 2003-10-16 19:38:27 | Re: Remote updating |