From: | Alex Hochberger <alex(at)dsgi(dot)us> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Configuring a Large RAM PostgreSQL Server |
Date: | 2007-11-29 19:21:10 |
Message-ID: | 8DC76DFA-C278-4C0C-A1FC-037257903BAD@dsgi.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
It's not on rebuilding the index, it's on CREATE INDEX.
I attribute it to wrong setting, Ubuntu bizarre-ness, and general
problems.
We need new hardware, the servers are running on aging
infrastructure, and we decided to get a new system that will last us
the next 3-4 years all at once.
But many large queries are getting Out of Memory errors.
Alex
On Nov 29, 2007, at 2:15 PM, Richard Huxton wrote:
> Alex Hochberger wrote:
>> Does anyone have any white papers or basic guides for a large RAM
>> server?
>> We are consolidating two databases to enable better data-mining
>> that currently run on a 4 GB and 2 GB machine. The data issues on
>> the 4 GB machine are numerous, things like "create index" fail and
>> update queries fail from out of memory issues.
>
>> Problem Usage: we have a 20GB table with 120m rows that we are
>> splitting into some sub-tables. Generally, we do large data pulls
>> from here, 1 million - 4 million records at a time, stored in a
>> new table for export. These queries are problematic because we
>> are unable to index the database for the queries that we run
>> because we get out of memory errors.
>
> Would it not make sense to find out why you are getting these
> errors first?
>
> It's not normal to get "out of memory" when rebuilding an index.
>
> --
> Richard Huxton
> Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-11-29 19:29:19 | Re: Configuring a Large RAM PostgreSQL Server |
Previous Message | Richard Huxton | 2007-11-29 19:15:15 | Re: Configuring a Large RAM PostgreSQL Server |