Re: Reorganization of spinlock defines

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reorganization of spinlock defines
Date: 2003-09-12 03:09:23
Message-ID: 5992.1063336163@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I guess we could splatter a test for Itanium and Opterion in every port
> that could possibly use it, but then again, if we fall back to not
> finding it for some reason, we don't get a report because we silently
> fall back to semaphores. That's what has me worried, that if we don't
> do it, we will not know what platforms really aren't working properly.

Agreed, the silent fallback to semaphores isn't such a hot idea in
hindsight. But the part of the patch that requires a configure option
to use that code path could be applied without touching anything else.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-09-12 03:13:54 Re: [HACKERS] Reorganization of spinlock defines
Previous Message Tom Lane 2003-09-12 03:04:09 Re: Reorganization of spinlock defines

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2003-09-12 03:13:54 Re: [HACKERS] Reorganization of spinlock defines
Previous Message Tom Lane 2003-09-12 03:04:09 Re: Reorganization of spinlock defines