From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Browne <cbbrowne(at)acm(dot)org> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 100 simultaneous connections, critical limit? |
Date: | 2004-01-14 15:04:53 |
Message-ID: | 3597.1074092693@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Christopher Browne <cbbrowne(at)acm(dot)org> writes:
> Clinging to sanity, jonr(at)physicallink(dot)com (Jn Ragnarsson) mumbled into her beard:
>> Then I read somewhere that Postgres only supports 100 simultaneous
>> connections (default).
> I thought the out-of-the-box default was 32.
Pre-7.4 it was 32; in 7.4 it's 100 (if your kernel settings will allow it).
It's important to point out that both of these are trivial-to-alter
configuration settings, not some kind of hardwired limit. However, the
more backend processes you have, the more RAM you need on the database
server. It's good advice to look into connection pooling instead of
trying to push max_connections up to the moon.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2004-01-14 17:09:23 | Re: 100 simultaneous connections, critical limit? |
Previous Message | Nick Barr | 2004-01-14 14:00:52 | Re: 100 simultaneous connections, critical limit? |