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

Re: fork/exec

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
Cc: "'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-28 16:30:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32
Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)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

In response to


pgsql-hackers-win32 by date

Next:From: Joshua D. DrakeDate: 2003-11-28 19:11:54
Subject: pg_ctl
Previous:From: Claudio NatoliDate: 2003-11-27 08:46:32
Subject: Re: fork/exec

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