Re: fork/exec - Mailing list pgsql-hackers-win32

From Tom Lane
Subject Re: fork/exec
Date
Msg-id 28525.1070037056@sss.pgh.pa.us
Whole thread Raw
In response to Re: fork/exec  (Claudio Natoli <claudio.natoli@memetrics.com>)
Responses Re: fork/exec  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers-win32
Claudio Natoli <claudio.natoli@memetrics.com> writes:
> * 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).

Cluttering the backend command line with intra-shmem addresses is messy
and unnecessary.  The shmem index map (see ShmemInitStruct) was designed
to allow backends to discover this stuff for themselves, and we should
resurrect that function.

            regards, tom lane

pgsql-hackers-win32 by date:

Previous
From: Claudio Natoli
Date:
Subject: Re: fork/exec
Next
From: "Joshua D. Drake"
Date:
Subject: pg_ctl