Re: fork/exec - Mailing list pgsql-hackers

From Claudio Natoli
Subject Re: fork/exec
Date
Msg-id A02DEC4D1073D611BAE8525405FCCE2B55F2B4@harris.memetrics.local
Whole thread Raw
In response to fork/exec  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: fork/exec  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

> It needs rewritten.  The hacks inserted for ExecBackend have largely
> destroyed the former structure (such as it was), and the lack of any
> commentary added with said hacks didn't help.  I am thinking 
> of tackling that rewrite once the dust has settled.

Anything in particular? 

With your SubPostmaster suggestion, the split of BackendRun (ne:
BackendFork) and BackendInit could now be undone (and I had a TODO item to
ask the list if such a reversion was desirable, and provide said patch)...
but other than that I don't see where any former structure re: backend
creation has been destroyed.

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: Claudio Natoli
Date:
Subject: Re: fork/exec
Next
From: Tom Lane
Date:
Subject: Re: fork/exec