Re: removing old ports and architectures - Mailing list pgsql-hackers

From Robert Haas
Subject Re: removing old ports and architectures
Date
Msg-id CA+TgmobbaHUGADjQVgtNJ_iYZyhjggqiGNLCsPceQ3JqyQ0=gA@mail.gmail.com
Whole thread Raw
In response to Re: removing old ports and architectures  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: removing old ports and architectures  (Tim Kane <tim.kane@gmail.com>)
Re: removing old ports and architectures  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-hackers
On Thu, Oct 17, 2013 at 5:41 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On 10/17/13 12:45 PM, Robert Haas wrote:
>> The attached patch, which I propose to apply relatively soon if nobody
>> objects, removes the IRIX port.
>
> +1

Done.  And here's a patch for removing the alpha architecture and
Tru64 UNIX (aka OSF/1) which runs on that architecture, per discussion
upthread.  Barring objections, I'll apply this next week.

On a related note, I think we should update the paragaraph in
installation.sgml that begins "In general, PostgreSQL can be expected
to work on these CPU architectures".  Any architecture that doesn't
have a buildfarm animal should be relegated to the second sentence,
which reads "Code support exists for ... but these architectures are
not known to have been tested recently."  Similarly, I think the
following paragraph should be revised so that only operating systems
for which we have current buildfarm support are considered fully
supported.  Others should be relegated to a sentence later in the
paragraph that says something like "code support exists but not tested
recently" or "expected to work but not tested regularly".

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

Attachment

pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: Adding new syntax in postgre sql
Next
From: Andrew Dunstan
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement