| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Remove Deprecated Exclusive Backup Mode |
| Date: | 2019-02-25 21:59:11 |
| Message-ID: | 65E67987-40D0-44C7-9AF5-6DAD74461DD9@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Feb 25, 2019, at 13:38, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> I think you might be right about this specific issue. But to me it
> sounds like you also don't appreciate that development resources are
> really constrained too, and providing endless backward compatibility for
> everything is going to use both resources directly, and indirectly by
> making the whole system more complex.
One of the things I've tried not to do in this discussion is turn it into a policy debate about backwards compatibility in general, rather than this very specific feature. Of course, there's a cost to keeping around features, and I fully appreciate that. In this discussion, the code complexity didn't seem to be the fundamental driver behind removing the feature; the relative safety of it was, along with maintaining the documentation.
I jumped in because there seemed to be an argument going on that all of the cool kids will have moved off the old interface and there was essentially no cost to removing it in v12 or v13, and that didn't correspond to my experience.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-02-25 22:07:40 | Re: POC: converting Lists into arrays |
| Previous Message | Andres Freund | 2019-02-25 21:51:04 | Re: POC: converting Lists into arrays |