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: | 6501.977339368@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Kovacs Zoltan Sandor | 2000-12-20 21:15:54 | Re: RE: version numbers of WinODBC |
Previous Message | Marc SCHAEFER | 2000-12-20 19:04:50 | Re: Re: [ADMIN] Help me for "DBI->connect failed: Sorry, too many clients already." |