Re: PostgreSQL for VAX on NetBSD/OpenBSD

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Thor Lancelot Simon <tls(at)panix(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, John Klos <john(at)ziaspace(dot)com>, port-vax(at)netbsd(dot)org, vax(at)openbsd(dot)org, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL for VAX on NetBSD/OpenBSD
Date: 2014-07-17 11:47:28
Message-ID: CA+TgmobzXCseKiV6gm-YiwrLqE4YzVg1Sq1mC8cgOv9iQrQm1w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 16, 2014 at 11:45 PM, Thor Lancelot Simon <tls(at)panix(dot)com> wrote:
> Well, I have to ask this question: why should there be any "vax-specific
> code"? What facilities beyond what POSIX with the threading extensions
> offers on a modern system do you really need? Why?

We have a spinlock implementation. When spinlocks are not available,
we have to fall back to using semaphores, which is much slower.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thor Lancelot Simon 2014-07-17 13:27:33 Re: PostgreSQL for VAX on NetBSD/OpenBSD
Previous Message Magnus Hagander 2014-07-17 11:21:00 Re: [bug fix] pg_ctl always uses the same event source