Re: removing old ports and architectures

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: removing old ports and architectures
Date: 2013-10-17 12:10:59
Message-ID: CA+TgmoZHgv_gowyFVCRYETihPWNTtK1DYeA-o3f5+puE3TweaQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 17, 2013 at 12:22 AM, Noah Misch <noah(at)leadboat(dot)com> wrote:
> Removing support for alpha is a different animal compared to removing support
> for non-gcc MIPS and most of the others in your list. A hacker wishing to
> restore support for another MIPS compiler would fill in the assembly code
> blanks, probably using code right out of an architecture manual. A hacker
> wishing to restore support for alpha would find himself auditing every
> lock-impoverished algorithm in the backend.

I had much the same thought last night. So I reverse my vote on
Alpha: let's drop it. I had thought that perhaps there'd be some
value in keeping it to force ourselves to consider what will happen
under the weakest generally-understood memory model, but in fact
that's probably a doomed effort without having the hardware available
to test the code. As you say, any future atomics support for such a
platform will be a major undertaking.

--
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 Robert Haas 2013-10-17 12:18:32 Re: ERROR : 'tuple concurrently updated'
Previous Message Robert Haas 2013-10-17 12:06:14 Re: [PATCH] pg_sleep(interval)