Re: LWLock/ShmemIndex startup question

From: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
To: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, 'Tom Lane ' <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "''''pgsql-hackers(at)postgresql(dot)org' ' ' '" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: LWLock/ShmemIndex startup question
Date: 2004-01-13 09:44:11
Message-ID: A02DEC4D1073D611BAE8525405FCCE2B55F25D@harris.memetrics.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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>

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2004-01-13 12:42:41 Re: Encoding problems in PostgreSQL with XML data
Previous Message Christopher Kings-Lynne 2004-01-13 08:19:15 Re: Reserved words and named function parameters