On Jan 7, 2016, at 10:32 PM, Sachin Srivastava <ssr.teleatlas@xxxxxxxxx> wrote: > > > Dear John, > > We are looking at more like 500-600 connections simultaneously in 1 day and I want to say we get 10000 to 12000 connections a day per db. Unless you have 300 cores to service those 500-600 simultaneous connections, you are really going to want to put your database behind a connection pooler such as pgBouncer. A connection pooler is a proxy that decreases the concurrency on the database, letting the database see only a few of the connections that clients want to make, and thereby increasing overall query throughput. If it works for your application, pgBouncer has wonderful mode called transaction pooling, which automatically rotates clients into an open database slot on transaction boundaries. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
