From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexaki Sofia <alexaki@ics.forth.gr>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Shared Memory: out of memory
Date: Wed, 20 Dec 2000 14:09:28 -0500
Message-ID: <6501.977339368@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.4.10.10012191644110.21249-100000@athena.ics.forth.gr>
References: <Pine.GSO.4.10.10012191644110.21249-100000@athena.ics.forth.gr>
Alexaki Sofia <alexaki@ics.forth.gr> writes:
> 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
You could try increasing the NLOCKS_PER_XACT space-estimation parameter
in src/include/storage/lock.h. However, I'd advise rethinking your
database design instead. 200000 tables will incur all sorts of
performance penalties, starting with long Unix directory search times.
You'll be much better off if you put the same data into fewer tables
(probably with more columns).
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, alexaki@ics.forth.gr
Subject: Re: Shared Memory: out of memory
In-Reply-To: <6501.977339368@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox