From: "Sorin N. Ciolofan" <ciolofan@ics.forth.gr>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>
Cc: <pgsql-general@postgresql.org>, <pgsql-admin@postgresql.org>,
	<pgsql-performance@postgresql.org>
Subject: Re: [GENERAL] ERROR: out of shared memory 
Date: Tue, 27 Mar 2007 16:13:42 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
thread-index: AcdwIUsgxMJeBjGfS6KihRH9XjNwhQAUGMAg
In-Reply-To: <11069.1174966638@sss.pgh.pa.us>
Message-Id: <20070327131301.065E38E40FC@mailhost.ics.forth.gr>

Dear Mr. Tom Lane,

Thank you very much for your answer.
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?

With best regards,
Sorin

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Tuesday, March 27, 2007 6:37 AM
To: Sorin N. Ciolofan
Cc: pgsql-general@postgresql.org; pgsql-admin@postgresql.org;
pgsql-performance@postgresql.org
Subject: Re: [GENERAL] ERROR: out of shared memory 

"Sorin N. Ciolofan" <ciolofan@ics.forth.gr> writes:
>    I have to manage an application written in java which call another
module
> written in java which uses Postgre DBMS in a Linux environment. I'm new to
> Postgres. The problem is that for large amounts of data the application
> throws an:
>  org.postgresql.util.PSQLException: ERROR: out of shared memory

AFAIK the only very likely way to cause that is to touch enough
different tables in one transaction that you run out of lock entries.
While you could postpone the problem by increasing the
max_locks_per_transaction setting, I suspect there may be some basic
application misdesign involved here.  How many tables have you got?

			regards, tom lane