> I am still wondering why postmaster fork/exec instead of
> just forking when receiving a new connection.
> Fork on modern unices (linux and (a think) *BSD) cost
> almost nothing (in time and memory) thanks to COW (copy-on-write).
> Exec in expensive as it breaks COW.
> I know this is not the time (have too wait 'til after 6.3),
> but shouldn't this be on the ToDo-list.
It was on my personal TODO. It is on the main one now:
* remove fork()/exec() of backend and make it just fork()
I had hoped to do this fir 6.3 as it will save 0.01 seconds on startup,
but no luck.
In response to
pgsql-hackers by date
|Next:||From: Tom||Date: 1998-01-24 21:35:33|
|Subject: Re: [HACKERS] fork/exec for backend|
|Previous:||From: Bruce Momjian||Date: 1998-01-24 20:25:08|
|Subject: Re: [HACKERS] Re: Browsing the tables and why pgsql does not perform well|