On Wed, Mar 5, 2014 at 2:09 AM, Sawada Masahiko <sawada.m...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers