Message-ID: <3A401C5D.AD66E52C@selectacast.net>
Date: Tue, 19 Dec 2000 21:41:33 -0500
From: Joseph Shraibman <jks@selectacast.net>
Organization: Xtenit, Inc. http://www.xtenit.com
MIME-Version: 1.0
To: Alexaki Sofia <alexaki@ics.forth.gr>
CC: pgsql-interfaces@postgresql.org
Subject: Re: Shared Memory: out of memory
References: <Pine.GSO.4.10.10012191644110.21249-100000@athena.ics.forth.gr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

200000 tables is rather a lot.  As I'm sure someone on hackers will tell
you, postgres is not designed to handle such bad database design.

Alexaki Sofia wrote:
> 
> Hello,
> 
> I'm working with the JDBC driver from the Postgresql 7.0.2 distribution.
> 
> My application creates transactions consisting of about 3000
> updates operations ('insert into table'  and 'create table').
> My database consists of a huge (200000) number of tables which
> form a hierarchy.
> 
> The postmaster throws the following error massage
> 
> >NOTICE:  ShmemAlloc: out of memory
> >FATAL 1:  LockAcquire: lock table 1 is corrupted
> 
> What can have caused this error? How can I overcome it?
> Should I define the parameter -B of the postmaster?
> 
> Thank you in advance
> Sofia Alexaki

-- 
Joseph Shraibman
jks@selectacast.net
Increase signal to noise ratio.  http://www.targabot.com