From: Christopher Browne <cbbrowne@acm.org>
Subject: Re: pgpool
Date: Thu, 06 Jul 2006 08:42:17 -0400
Organization: cbbrowne Computing Inc
Lines: 31
Message-ID: <87lkr6x5ue.fsf@wolfe.cbbrowne.com>
References: <1c66bda80607052157m51c61e81x4e5f2774dfa1300a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux)
Cancel-Lock: sha1:DMJUNFKUz9IQ0+p7bpV+sJbMA4c=
To: pgsql-admin@postgresql.org

After a long battle with technology, adey11@gmail.com (adey), an earthling, wrote:
> Please could someone give me an idea of what pgpool is, and where I can research it?
>
> I have run a search on postgresql.org and found many references, but
> they don't explain what it is, and it doesn't appear in the
> documentation index of the v8.1 manuals.

It's not officially part of the database, so no, it's not in the
database documentation.

<http://pgpool.projects.postgresql.org/>

It's a connection pool server implemented in C...  The notion is that
you run your database on (say) port 5432, and then put pgpool in
between, on port 4432.

pgpool opens up some fixed number of connections to the database,
keeping them open, and your application connects to port 4432, as if
it were a direct connection to the database.

pgpool then manages the connections, basically keeping them open
irrespective of how your application handles connections.

This can be a big help to performance if your application is pretty
loose about opening and closing connections whenever it likes.
-- 
(reverse (concatenate 'string "moc.liamg" "@" "enworbbc"))
http://linuxdatabases.info/info/lsf.html
The real  problem with the  the year 2000  is that there are  too many
zero bits and that adversely affects the global bit density.
-- Boyd Roberts <boyd@france3.fr>