Re: fork/exec
От | Claudio Natoli |
---|---|
Тема | Re: fork/exec |
Дата | |
Msg-id | A02DEC4D1073D611BAE8525405FCCE2B02805A@harris.memetrics.local обсуждение исходный текст |
Список | 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. Worked a treat. I've created a new spin lock. Should I send along a patch, or instead try to use the existing ShmemLock? (Note that, since ShmemAlloc locks/releases ShmemLock, ShmemInitStruct would have to in some way indicate to ShmemAlloc that it was already holding... which I can't imagine anyone is too keen on). 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 по дате отправления: