From: Adam Alkins <postgresql@rasadam.com>
To: pgsql-performance@postgresql.org
Subject: Re: 100 simultaneous connections, critical limit?
Date: Wed, 14 Jan 2004 14:10:14 -0400
Message-ID: <40058606.10605@rasadam.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0401140956040.24964-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0401140956040.24964-100000@css120.ihs.com>
scott.marlowe wrote:
>A few tips from an old PHP/Apache/Postgresql developer.
>
>1: Avoid pg_pconnect unless you are certain you have load tested the
>system and it will behave properly. pg_pconnect often creates as many
>issues as it solves.
>
>
I share the above view. I've had little success with persistent
connections. The cost of pg_connect is minimal, pg_pconnect is not a
viable solution IMHO. Connections are rarely actually reused.
--
Adam Alkins
http://www.rasadam.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: postgresql@rasadam.com
Subject: Re: 100 simultaneous connections, critical limit?
In-Reply-To: <40058606.10605@rasadam.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox