Re: ShmemAlloc errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nick Burrett <nick(at)dsvr(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ShmemAlloc errors
Date: 2003-10-17 13:49:14
Message-ID: 22143.1066398554@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Nick Burrett <nick(at)dsvr(dot)net> writes:
> Tom Lane wrote:
>> We don't normally hear of people needing that --- is there anything
>> unusual about the schema of this database?

> Not particularly. The database consists of around 3000 tables created
> using this:

> CREATE TABLE vs_foo (date date NOT NULL,
> time time NOT NULL,
> bytesin int8 CHECK (bytesin >= 0),
> bytesout int8 CHECK (bytesout >= 0));

> Each table has around 1500 rows.

3000 tables? That's why you need so many locks. Have you thought about
collapsing these into *one* table with an extra key column? Also, it'd
likely be better to combine the date and time into a timestamp column.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nick Burrett 2003-10-17 14:00:59 Re: ShmemAlloc errors
Previous Message Shridhar Daithankar 2003-10-17 13:42:24 Re: VACUUM degrades performance significantly. Database