From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Igor Neyman <ineyman(at)perceptron(dot)com> |
Cc: | Serge Fonville <serge(dot)fonville(at)gmail(dot)com>, mgould(at)isstrucksoftware(dot)net, Durumdara <durumdara(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Stability in Windows? |
Date: | 2012-02-24 20:33:24 |
Message-ID: | CAOR=d=0UqcgnuBneHR0aBMx5Ocib6hj6acvKa63jkRVZkzus=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Feb 24, 2012 at 12:58 PM, Igor Neyman <ineyman(at)perceptron(dot)com> wrote:
> “125_connections” – this is a problem related to “older” PG versions (and in
> my own experience, the number is closer to 230, not 125), and I believe it
> was fixed in newer versions.
>
> Besides, it’s much more efficient to use connection pulling (PgBouncer,
> PgPool), when dealing with that many connections.
Agreed. Note that in some big environments you're using pgbouncer to
reduce thousands of connections to a few hundred. In those instances.
At that point having 40+ cores and running on unix becomes necessary
for performance with pgsql.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2012-02-24 20:35:25 | Re: Maxium Share Memory in Debian 64bit |
Previous Message | Scott Marlowe | 2012-02-24 20:31:34 | Re: Re: When I try to connect to a database, I get the following error : psql teleflowdb8 |