Re: max_connections

From: jam3 <jamorton3(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: max_connections
Date: 2012-09-05 20:51:47
Message-ID: 1346878307201-5722899.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

According to

http://www.postgresql.org/docs/8.3/static/kernel-resources.html

The maximum shared memory usage of a connection in bytes is

1800 + 270 * max_locks_per_transaction

max_locks_per_transaction default is 64

19080 Bytes

or .018 mb's per connection

or

1.819 mb at 100 default connections

With a Gig of Phsical Ram setting Shared Buffers to use 25% - 256 mb
dedicated to Postgres

default is using roughly 0.75% for connections

You can extrapolate this out taking into consideration all your specific
variables, total physical RAM, postgresql.conf settings etc but I wouldn;t
run off to use pgpool unless your in an extremly connection heavy
environment as it does add an additional layer within the client server
connection and is another component to config and admin.

--
View this message in context: http://postgresql.1045698.n5.nabble.com/max-connections-tp5722890p5722899.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2012-09-05 21:02:13 Re: Where is the char and varchar length in pg_catalog for function input variables
Previous Message Kevin Grittner 2012-09-05 20:42:28 Re: max_connections