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

From Robert Haas
Subject Re: Defaults for replication/backup
Date
Msg-id CA+TgmoaohvVD27dP5e=pfMjOYqbnxafvU3B5C5R7WsQONr=o-g@mail.gmail.com
Whole thread Raw
In response to Re: Defaults for replication/backup  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Defaults for replication/backup  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parser extensions (maybe for 10?)
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Move each SLRU's lwlocks to a separate tranche.