Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] ERROR: out of shared memory

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 (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-generalpgsql-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

In response to

Responses

pgsql-performance by date

Next:From: Michael DenglerDate: 2007-03-27 22:16:28
Subject: How to enable jdbc???
Previous:From: Sorin N. CiolofanDate: 2007-03-27 13:13:42
Subject: Re: [GENERAL] ERROR: out of shared memory

pgsql-admin by date

Next:From: Bruce MomjianDate: 2007-03-27 15:36:31
Subject: Re: Priorities for users or queries?
Previous:From: Sorin N. CiolofanDate: 2007-03-27 13:13:42
Subject: Re: [GENERAL] ERROR: out of shared memory

pgsql-general by date

Next:From: Csaba NagyDate: 2007-03-27 14:05:09
Subject: Re: [OT] cutting out the middleperl
Previous:From: Merlin MoncureDate: 2007-03-27 13:56:47
Subject: Re: [OT] cutting out the middleperl

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group