Re: fork/exec - Mailing list pgsql-hackers

From Claudio Natoli
Subject Re: fork/exec
Date
Msg-id A02DEC4D1073D611BAE8525405FCCE2B55F2B3@harris.memetrics.local
Whole thread Raw
In response to fork/exec  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: fork/exec  ("Andrew Dunstan" <andrew@dunslane.net>)
List pgsql-hackers
 
> Looking at postmaster.c, my head started to spin a little. I think I 
> understood that exec case or not, by the time we get to BackendRun we 
> have already done all the fork/exec action. Have I read this correctly?

Yes. In the normal case, fork() then BackendRun. In the EXEC_BACKEND case,
fork/exec (or CreateProcess), which then invokes BackendRun via
SubPostmasterMain.


> (This code is getting rather intricate. A Readme file might be nice. 
Just a thought)

Which bits in particular?

Cheers,
Claudio

--- 
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see 
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Idea about better configuration options for sort memory
Next
From: Claudio Natoli
Date:
Subject: Re: fork/exec