Re: PostgreSQL pre-fork speedup

sdv mailer wrote:
> I'm talking about connecting to multiple database
> servers on separate machines. Schemas don't apply
> here.
> 
> How much work would it take to make a pre-fork smart
> enough to open different databases on incoming
> connection? How much of it can be modeled after
> Apache?
> 

I've not used it but Tatsuo Ishii has just released pgpool v1.0. Quoting 
from its README:

1. What is pgpool

    pgpool is a connection server program for PostgreSQL. pgpool runs
    between PostgreSQL's client(frontend) and server(backend). Any
    PostgreSQL clients can connect to pgpool as if it's a real
    PostgreSQL server.

    pgpool caches the connection to PostgreSQL server to reduce the
    overhead to establish the connection to it.

    Also pgpool could use two PostgreSQL servers for fail over
    purpose. If the first server goes down, pgpool will automatically
    switch to the secondary server.

If that's not what you're after, then it must be fairly close. Check the 
mailing list archives - the download URL is on the "announce" list April 
2004.

I'm sure any real figures from your testing will be of much interest to 
all of us.

HTH
-- 
   Richard Huxton
   Archonet Ltd