| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Sorin N(dot) Ciolofan" <ciolofan(at)ics(dot)forth(dot)gr> |
| Cc: | pgsql-general(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] ERROR: out of shared memory |
| Date: | 2007-03-27 13:59:15 |
| Message-ID: | 19352.1175003955@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general pgsql-performance |
"Sorin N. Ciolofan" <ciolofan(at)ics(dot)forth(dot)gr> writes:
> It seems that the legacy application creates tables dynamically and the
> number of the created tables depends on the size of the input of the
> application. For the specific input which generated that error I've
> estimated a number of created tables of about 4000.
> Could be this the problem?
If you have transactions that touch many of them within one transaction,
then yup, you could be out of locktable space. Try increasing
max_locks_per_transaction.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-03-27 15:36:31 | Re: Priorities for users or queries? |
| Previous Message | Sorin N. Ciolofan | 2007-03-27 13:13:42 | Re: [GENERAL] ERROR: out of shared memory |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2007-03-27 14:05:09 | Re: [OT] cutting out the middleperl |
| Previous Message | Merlin Moncure | 2007-03-27 13:56:47 | Re: [OT] cutting out the middleperl |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Dengler | 2007-03-27 22:16:28 | How to enable jdbc??? |
| Previous Message | Sorin N. Ciolofan | 2007-03-27 13:13:42 | Re: [GENERAL] ERROR: out of shared memory |