Re: Parameter oddness; was HS/SR Assert server crash

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parameter oddness; was HS/SR Assert server crash
Date: 2010-05-14 21:19:03
Message-ID: 4BED77F702000025000317C6@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> One odd thing is we have two paramters that mention hot_standby
> --- on the master we have to do in postgresql.conf:
>
> wal_level = hot_standby
>
> and on the slave we do in postgresql.conf:
>
> hot_standby = on
>
> That is a little confusing.

Why? I read that as saying that the master is writing sufficient
data into the WAL for it to be usable for hot standby purposes, and
that that the slave machine is going to be used as a hot standby.
You'd better do the former if you're going to do the latter, but
there were good reasons not to try to infer one setting from the
other.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-05-14 21:23:18 Re: recovery consistent != hot standby
Previous Message Bruce Momjian 2010-05-14 21:12:09 Re: Parameter oddness; was HS/SR Assert server crash