Re: LWLock/ShmemIndex startup question - Mailing list pgsql-hackers

From Claudio Natoli
Subject Re: LWLock/ShmemIndex startup question
Date
Msg-id A02DEC4D1073D611BAE8525405FCCE2B55F25D@harris.memetrics.local
Whole thread Raw
In response to LWLock/ShmemIndex startup question  (Claudio Natoli <claudio.natoli@memetrics.com>)
Responses Re: LWLock/ShmemIndex startup question
List pgsql-hackers
> Ok, I think having a native win32 spin-lock implementation 
> (say, based on InterlockedCompareExchange?) is the minimal 
> impact answer. I'll work on producing that.

Or, maybe we'll just use the tas() implementation that already exists for
__i386__/__x86_64__ in s_lock.h. How did I miss that?

Move along. Nothing to see here.

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 by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Reserved words and named function parameters
Next
From: Hannu Krosing
Date:
Subject: Re: Encoding problems in PostgreSQL with XML data