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

From Claudio Natoli
Subject Re: fork/exec
Date
Msg-id A02DEC4D1073D611BAE8525405FCCE2B028057@harris.memetrics.local
Whole thread Raw
List pgsql-hackers-win32

> 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>

pgsql-hackers-win32 by date:

Previous
From: Tom Lane
Date:
Subject: Re: fork/exec
Next
From: Claudio Natoli
Date:
Subject: Re: fork/exec