Re: allowing wal_level change at run time

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: allowing wal_level change at run time
Date: 2015-08-23 03:18:55
Message-ID: 55D93B9F.9060707@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/20/15 3:50 PM, Andres Freund wrote:
>> But, under any scheme to set wal_level automatically, how will the
>> primary know whether it needs to use level archive or hot_standby?
>
> I'd have said archive_mode triggered archive and everything else
> hot_standby.

That might be a decent heuristic, but it's not correct if there is no
way to override it. People are using archive-only replication with hot
standby (for delayed replication, for example).

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2015-08-23 03:42:48 Re: checkpointer continuous flushing
Previous Message Tomas Vondra 2015-08-23 00:34:53 Re: PATCH: numeric timestamp in log_line_prefix