Re: Getting rid of wal_level=archive and default to hot_standby + wal_senders - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Getting rid of wal_level=archive and default to hot_standby + wal_senders
Date
Msg-id 3586.1422978064@sss.pgh.pa.us
Whole thread Raw
In response to Getting rid of wal_level=archive and default to hot_standby + wal_senders  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Getting rid of wal_level=archive and default to hot_standby + wal_senders  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> Additionally I think we should change the default for wal_level to
> hot_standby and max_wal_senders (maybe to 5). That way users can use
> pg_basebackup and setup streaming standbys without having to restart the
> primary. I think that'd be a important step in making setup easier.

I always thought the reason for defaulting to "minimal" was performance.
I'd like to see proof that the impact of wal_level = hot_standby is
negligible before we consider doing this.

The argument that having to change one more GUC is an undue burden while
configuring hot standby seems ridiculous from here.  HS is not nearly
"push the EASY button and you're done", and this change wouldn't make
it so.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: REINDEX CONCURRENTLY 2.0
Next
From: Heikki Linnakangas
Date:
Subject: Re: Redesigning checkpoint_segments