Re: Cleaning up historical portability baggage

From: Michael Banck <mbanck(at)gmx(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cleaning up historical portability baggage
Date: 2025-06-09 15:40:50
Message-ID: 68470082.050a0220.2e3c98.49cc@mx.google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Mon, Jun 09, 2025 at 10:25:23AM -0400, Andres Freund wrote:
> I think our policy basically is that if it doesn't exist on the BF, it's
> unsupported. Also note that Hurd is not listed as a supported OS:
> https://www.postgresql.org/docs/devel/supported-platforms.html
>
> We can't design for OS that we don't know it's used with postgres and/or how
> that OS works / what it supports.
>
> So I reject the premise that this is a regression.

Fair enough. I'll see whether I can get a BF animal going for it at some
point.

Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Florents Tselai 2025-06-09 15:54:16 Re: Feature: psql - display current search_path in prompt
Previous Message Tomas Vondra 2025-06-09 15:34:14 Re: Amcheck verification of GiST and GIN