Re: [HACKERS] fork/exec for backend

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: goran(at)bildbasen(dot)se (Goran Thyni)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] fork/exec for backend
Date: 1998-01-24 20:45:48
Message-ID: 199801242045.PAA07890@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
>
> 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.

--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom 1998-01-24 21:35:33 Re: [HACKERS] fork/exec for backend
Previous Message Bruce Momjian 1998-01-24 20:25:08 Re: [HACKERS] Re: Browsing the tables and why pgsql does not perform well