From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Subject: Re: pg_dump versus ancient server versions
Date: Mon, 25 Oct 2021 12:05:22 -0300
Message-ID: <202110251505.vo3krfhxi2ci@alvherre.pgsql> (raw)
In-Reply-To: <3883429.1635171820@sss.pgh.pa.us>
On 2021-Oct-25, Tom Lane wrote:
> Roughly speaking, I think the policy should be "no feature bug fixes,
> not even security fixes, for EOL'd branches; only fixes that are
> minimally necessary to make it build on newer platforms". And
> I want to have a sunset provision even for that. Fixing every branch
> forevermore doesn't scale.
Agreed. I think dropping such support at the same time we drop
psql/pg_dump support is a decent answer to that. That meets the stated
purpose of being able to test such support, and also it moves forward
according to subjective choice per development needs.
> Also, I concur with Andrew's point that we'd really have to have
> buildfarm support. However, this might not be as bad as it seems.
> In principle we might just need to add resurrected branches back to
> the branches_to_build list.
Well, we would add them to *some* list, but not to the one used by stock
BF members -- not only because of the diskspace issue but also because
of the time to build. I suggest that we should have a separate
list-of-branches file that would only be used by BF members especially
configured to do so; and hopefully we won't allow more than a handful
animals to do that but rather a well-chosen subset, and also maybe allow
only GCC rather than try to support other compilers. (There's no need
to ensure compilability on any Windows platform, for example.)
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
"Ed is the standard text editor."
http://groups.google.com/group/alt.religion.emacs/msg/8d94ddab6a9b0ad3
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, andrew@dunslane.net, pgsql-hackers@lists.postgresql.org, andres@anarazel.de
Subject: Re: pg_dump versus ancient server versions
In-Reply-To: <202110251505.vo3krfhxi2ci@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox