Re: BUG #5756: postgres eat up all memory(2GB memory)

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: amos <amosleaf(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5756: postgres eat up all memory(2GB memory)
Date: 2010-11-18 07:37:51
Message-ID: 4CE4D7CF.3010200@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Amos"

This is not a bug. Your PostgreSQL install is misconfigured - you have
told it to use more memory than you have. Use a reasonable number of
max_connections, maybe as few as 20 or 30, and set c3p0 (your connection
pooler) to use one or two fewer than that. Your webapp's clients should
share the connections, and you should get MUCH, MUCH better results that
way, because your machine will spend less time thrashing and more time
getting real work done.

Feel free to ask for help on the postgresql-general mailing list if you
want further assistance.

http://www.postgresql.org/community/lists/

http://archives.postgresql.org/pgsql-general/

--
System & Network Administrator
POST Newspapers

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jon Nelson 2010-11-18 15:28:26 Re: Problem with ALTER TABLE - occasional "tuple concurrently updated"
Previous Message amos 2010-11-18 03:18:57 BUG #5756: postgres eat up all memory(2GB memory)