On Wed, Mar 5, 2014 at 5:13 PM, Amit Langote wrote:
> On Wed, Mar 5, 2014 at 12:07 PM, Amit Langote wrote:
>> On Wed, Mar 5, 2014 at 2:09 AM, Sawada Masahiko
>> wrote:
>>
>>>
>>> xlog.c:6177
>>> if (ControlFile->wal_level < WAL_LEVEL_HOT_STANDBY)
>>> ereport(ERROR,
>>> (errms
On Wed, Mar 5, 2014 at 12:07 PM, Amit Langote wrote:
> On Wed, Mar 5, 2014 at 2:09 AM, Sawada Masahiko 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
On Wed, Mar 5, 2014 at 2:09 AM, Sawada Masahiko 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_leve
On Wed, Mar 5, 2014 at 4:09 AM, Sawada Masahiko wrote:
> Hi all,
>
> I had doubts regarding behavior of CheckRequiredParameterValues() function.
>
> I could not start standby server which is created by pg_basebackup
> with following scenario.
> 1. Start the master server with 'wal_level = archve'
Hi all,
I had doubts regarding behavior of CheckRequiredParameterValues() function.
I could not start standby server which is created by pg_basebackup
with following scenario.
1. Start the master server with 'wal_level = archve' , 'hot_standby =
on' and other settings of replication.
2. Create th
