From: Neil Saunders <n.j.saunders@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: scaling up postgres
Date: Sat, 3 Jun 2006 16:35:54 +0100
Message-ID: <ddcd549e0606030835t7236a060g65f4061ac935828@mail.gmail.com> (raw)
In-Reply-To: <4481A856.7050907@boreham.org>
References: <200606030931.k539V38Y007877@smtp2.planet.net.tn>
<15971.1149347558@sss.pgh.pa.us>
<4481A856.7050907@boreham.org>
>
> Tom Lane wrote:
> As per PFC's comment, if connections/sec is a bottleneck for you then
the
> answer is to use persistent connections. Launching a new backend
is a fairly
> heavyweight operation in Postgres.
>
In which case maybe pgpool could help in this respect?
http://pgpool.projects.postgresql.org/
Cheers,
Neil.
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: n.j.saunders@gmail.com
Subject: Re: scaling up postgres
In-Reply-To: <ddcd549e0606030835t7236a060g65f4061ac935828@mail.gmail.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