| From: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> |
|---|---|
| To: | 'Andrew Dunstan ' <andrew(at)dunslane(dot)net>, 'PostgreSQL-development ' <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fork/exec |
| Date: | 2004-02-01 23:11:43 |
| Message-ID: | A02DEC4D1073D611BAE8525405FCCE2B55F2B3@harris.memetrics.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Natoli | 2004-02-01 23:33:23 | Re: fork/exec |
| Previous Message | Bruce Momjian | 2004-02-01 23:07:51 | Re: Idea about better configuration options for sort memory |