getting our bearings on "out of memory. failed on request of size..."

From: Tom Darci <tom(at)nuws(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: getting our bearings on "out of memory. failed on request of size..."
Date: 2008-10-28 14:03:18
Message-ID: C5ED5363-237A-42B5-855D-2BD65EE5AB31@nuws.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi All,

Our PG server is serving up 50 databases or so (with identical
schemas), and the largest one of those has started giving us "out of
memory. failed on request of size n" errors in many places. This is a
9 GB database with 100+ tables, the largest of which have 4 million or
so rows. We see the Out of Memory errors when trying to run a "hard"
SQL statement (SELECTing from a complex view, updating all rows in a
large table, etc...)

Can anybody point us in a good direction of how to track down just
why this is happening? Is there something we should be looking for in
the log (and log settings to turn on)? What is a good way to log
memory usage of statements?

Any help much appreciated in figuring out how to approach problems
like these.

Thanks,
-Tom

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Allan Kamau 2008-10-28 14:09:31 Re: Piping CSV data to psql when executing COPY .. FROM STDIN
Previous Message Reid Thompson 2008-10-28 13:58:57 Re: Piping CSV data to psql when executing COPY .. FROM STDIN