Getting rid of wal_level=archive and default to hot_standby + wal_senders

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Getting rid of wal_level=archive and default to hot_standby + wal_senders
Date: 2015-02-03 12:43:17
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


I think these days there's no reason for the split between the archive
and hot_standby wal levels. The split was made out of volume and
stability concerns. I think we can by now be confident about the
wal_level = hot_standby changes (note I'm not proposing hot_standby =

So let's remove the split. It just gives users choice between two options
that don't have a meaningful difference.

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.

Previously there have been arguments against changing the default of
wal_level because it'd mean the regression tests wouldn't exercise
minimal anymore. That might be true, but then right now we just don't
exercise the more complex levels. If we're really concerned we can just
force a different value during the tests, just as we do for prepared


Additionally, more complex and further into the future, I wonder if we
couldn't also get rid of wal_level = logical by automatically switching
to it whenever logical slots are active.


Andres Freund

Andres Freund
PostgreSQL Development, 24x7 Support, Training & Services


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2015-02-03 12:45:36 Re: Small memory leak in execute.c of ECPG driver
Previous Message Magnus Hagander 2015-02-03 12:36:08 Re: SSL information view