Re: PostgreSQL pre-fork speedup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Paul Ramsey <pramsey(at)refractions(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, sdv mailer <sdvmailer(at)yahoo(dot)com>
Subject: Re: PostgreSQL pre-fork speedup
Date: 2004-05-03 16:09:34
Message-ID: 14001.1083600574@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Paul Ramsey <pramsey(at)refractions(dot)net> writes:
> ... So the operational benefit of adding the complexity of a
> pre-fork system is not very high.

In particular, most of the connection startup overhead work cannot be
performed until we've identified which database to connect to (since
it largely consists of bootstrapping access to the system catalogs
in that database). If you want that work to be done in advance of
receiving a client connection request, life is much more complicated
than it would be for something like Apache.

There is considerable discussion of this point in the pgsql-hackers
archives. I'd suggest reading the past threads before trying to do
anything yourself.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Swan 2004-05-03 16:14:51 Re: inconsistent owners in newly created databases?
Previous Message olivia jurado 2004-05-03 16:05:09 I need Help