Re: The behavior of CheckRequiredParameterValues() - Mailing list pgsql-hackers

From Amit Langote
Subject Re: The behavior of CheckRequiredParameterValues()
Date
Msg-id CA+HiwqEb3CMHPc+u8tQvYD8uBsqU55vN4G6FUhag38XcKwYomA@mail.gmail.com
Whole thread Raw
In response to The behavior of CheckRequiredParameterValues()  (Sawada Masahiko <sawada.mshk@gmail.com>)
Responses Re: The behavior of CheckRequiredParameterValues()  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On Wed, Mar 5, 2014 at 2:09 AM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:

>
> xlog.c:6177
>  if (ControlFile->wal_level < WAL_LEVEL_HOT_STANDBY)
>      ereport(ERROR,
>              (errmsg("hot standby is not possible because wal_level was not
>
> So we have to start and stop standby server with changed
> wal_level(i.g., hot_standby) if we want to enable hot standby.
> In this case, I think that the standby server didn't need to confirm
> wal_level value of ControlFile.
> I think that it should confirm value which is written in postgreql.conf.
>

I think checking it from the control file on a standby in recovery
means that we should confirm if the *wal_level with which the WAL was
generated* is sufficient to now become a hot standby after recovery
finishes.

--
Amit



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Row-security on updatable s.b. views
Next
From: Craig Ringer
Date:
Subject: API change advice: Passing plan invalidation info from the rewriter into the planner?