From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Christophe Pettus <xof(at)thebuild(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 15:54:53 |
Message-ID: | CA+TgmobSR86jzYPAGLo6bZpDYhyU70wo39NBa2FGU2pSq+WvEw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Feb 24, 2019 at 3:00 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Ok, then please do so, and please be prepared to continue to maintain
> the documentation of both methods moving forward, because others have
> tried and have (rightfully, in my opinion) decided that it's frankly not
> worth the effort and ultimately just terribly confusing for users that
> we have these two different backup methods and even just updating the
> documentation for one or the other is downright painful (to the point
> that people litterally give up on it). That really isn't a good place
> to be in.
This, to me, is downright rude. You don't get to tell other people
what to do. Nor do you get to tell other people "hey, I'm going to
make this change that you don't like unless you agree to do the work
which I specify." If you want to make a change, you have to build
consensus for that change. If you can't get people to agree with your
proposed change, what happens is that you don't get to make that
change. Whether other people choose to do any work that you and they
might happen to agree is valuable is up to them.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-02-25 16:02:52 | Re: Remove Deprecated Exclusive Backup Mode |
Previous Message | Laurenz Albe | 2019-02-25 15:43:40 | Re: Should we increase the default vacuum_cost_limit? |