Re: pg_dump versus ancient server versions

On 02.12.21 23:16, Andres Freund wrote:
> I think we should at least include pg_upgrade in this as well, it's pretty
> closely tied to at least pg_dump.

right

>> * pg_dump and psql will maintain compatibility with servers at least
>> ten major releases back.
>
> Personally I think that's too long... It boils down keeping branches buildable
> for ~15 years after they've been released. That strikes me as pretty far into
> diminishing-returns, and steeply increasing costs, territory.

Well, it is a lot, but it's on the order of what we have historically
provided.

> I realize it's more complicated for users, but a policy based on supporting a
> certain number of out-of-support branches calculated from the newest major
> version is more realistic. I'd personally go for something like newest-major -
> 7 (i.e. 2 extra releases), but I realize that others think it's worthwhile to
> support a few more. I think there's a considerable advantage of having one
> cutoff date across all branches.

I'm not sure it will be clear what this would actually mean. Assume
PG11 supports back to 9.4 (14-7) now, but when PG15 comes out, we drop
9.4 support. But the PG11 code hasn't changed, and PG9.4 hasn't changed,
so it will most likely still work. Then we have messaging that is out
of sync with reality. I can see the advantage of this approach, but the
communication around it might have to be refined.

> I think we should explicitly limit the number of platforms we care about for
> this purpose. I don't think we should even try to keep 8.2 compile on AIX or
> whatnot.

It's meant to be developer-facing, so only for platforms that developers
use. I think that can police itself, if we define it that way.