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

Re: Shared Memory: out of memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexaki Sofia <alexaki(at)ics(dot)forth(dot)gr>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Shared Memory: out of memory
Date: 2000-12-20 19:09:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Alexaki Sofia <alexaki(at)ics(dot)forth(dot)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

In response to

pgsql-interfaces by date

Next:From: Kovacs Zoltan SandorDate: 2000-12-20 21:15:54
Subject: Re: RE: version numbers of WinODBC
Previous:From: Marc SCHAEFERDate: 2000-12-20 19:04:50
Subject: Re: Re: [ADMIN] Help me for "DBI->connect failed: Sorry, too many clients already."

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