Skip site navigation (1) Skip section navigation (2)

Re: fork/exec

From: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
To: 'Bruce Momjian' <pgman(at)candle(dot)pha(dot)pa(dot)us>,PostgreSQL Win32 port list <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: fork/exec
Date: 2003-11-27 08:46:32
Message-ID: A02DEC4D1073D611BAE8525405FCCE2B028050@harris.memetrics.local (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
Hi Bruce,

I have a couple of questions regarding your intended fork/exec changes
related to BackendFork:

* I see you are passing the values of things like UsedShmemSegID,
UsedShmemSegAddr etc on the command line. Was your intention to pass other
shared mem addresses like FreeSpaceMap, LWLockArray in this way too, or did
you intend to register these addresses within another section of shared
memory, or some other idea (FWIW, I've got a cygwin version fork/exec'ing
the backends using the former method).

* With regards to BackendFork itself, was your plan to reduce this to simply
formatting the argument list, and calling fork/exec, with things like random
number seeding and the like moved into PostgresMain? (ie. the BackendFork
call would actually be performed by the Postmaster, with BackendFork
rewritten such that no "global" context is required between the fork and
exec calls; which'll be what we need to make Win32/CreateProcess changes
possible). If not, could you give me an idea of what you had intended?

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>

Responses

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2003-11-28 16:30:56
Subject: Re: fork/exec
Previous:From: Steve TibbettDate: 2003-11-20 00:35:03
Subject: Re: [PATCHES] SRA Win32 sync() code

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group