Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: fork/exec
- From: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
- To: 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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: Mon, 1 Dec 2003 14:50:27 +1100
- Message-id: <A02DEC4D1073D611BAE8525405FCCE2B028057@harris.memetrics.local> <text/plain>
> Hm, seems messy. Note that setting up MyProc does *not* > require LWLock access, only a spinlock (which is obviously necessary > to avoid circularity). It might be best to replace ShmemIndexLock > with a spinlock to reduce the amount of infrastructure that has to be live > before we can make use of the shmem index hashtable. That looks like a great idea. > I don't want to abandon locking entirely, but I do think we can simplify > the lock type if it helps make the startup sequence easier. It would certainly do that. I'll take a look at it tonight... 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>
- Prev by Date: Re: fork/exec
- Previous by thread: Re: fork/exec
- Next by thread: pg_ctl
- Indexes: