Re: Cannot restart postgresql when increasing max_connections - Mailing list pgsql-general

From Thom Brown
Subject Re: Cannot restart postgresql when increasing max_connections
Date
Msg-id bddc86150901080521nf14b740s95420d11a8e6a8fe@mail.gmail.com
Whole thread Raw
In response to Re: Cannot restart postgresql when increasing max_connections  (Richard Huxton <dev@archonet.com>)
Responses Re: Cannot restart postgresql when increasing max_connections
List pgsql-general
This database server is currently serving 3 very very busy multi-core web servers, and we're about to add another 3 to help deal with the load.

I'm afraid that upgrading is not an option at present because it's in production.

I've taken the suggestion of increasing shared buffers and now got max_connections set to 1500 and shared_buffers set to about a gigabyte.

I actually mentioned pgPool II to my boss earlier, and it's something we will have to seriously consider, but will have to do some research first.

Thanks

Thom

2009/1/8 Richard Huxton <dev@archonet.com>
Thom Brown wrote:
> It is running on 64-bit Gentoo 2.6.25.
>
> You might be right about needing to increase the shared buffers.  Thanks for
> the suggestion.  I'll have to give that a try

If shared_buffers was so small that you can't handle the connections you
might benefit from one of the links on this page.

http://wiki.postgresql.org/wiki/Performance_Optimization

Try the first one, that gives you a good overview.

Oh and if you're running a web-application consider connection pooling -
pgbouncer or pgpool.

Oh, and upgrade from 8.3.1 to the latest in the 8.3 series at your
earliest convenience.

http://www.postgresql.org/support/versioning

--
 Richard Huxton
 Archonet Ltd

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Cannot restart postgresql when increasing max_connections
Next
From: "Josh Harrison"
Date:
Subject: Question about COPY command