Re: Defaults for replication/backup - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Defaults for replication/backup
Date
Msg-id CABUevExb78OLKaEOHCGiFOnSr6R1Ef5wQn1hCNZUdsZL17sF=w@mail.gmail.com
Whole thread Raw
In response to Re: Defaults for replication/backup  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Defaults for replication/backup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On Thu, Apr 21, 2016 at 7:20 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Wed, Apr 20, 2016 at 2:04 PM, Magnus Hagander <magnus@hagander.net> wrote:
> So what more do we need to just get going with this? Given feature freeze
> we're perhaps too late to actually build the parameter feature for initdb,
> but we could still change the defaults (and then we could add such a
> parameter for next release).

I think we are far too close to beta1 to begin bikeshedding this.
Changing the defaults is not going to be uncontroversial, and it's not
something I think we should rush into.


I think that may be a case of the good old letting perfection get in the way of progress. We can be pretty sure that whatever we decide to do (now or later) will not be perfect. But we can be equally sure that it will be better than what we have today in most cases. But that's just me... 

--

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Updated backup APIs for non-exclusive backups
Next
From: Stephen Frost
Date:
Subject: Re: Updated backup APIs for non-exclusive backups