Re: Synch Replication

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "K, Niranjan (NSN - IN/Bangalore)" <niranjan(dot)k(at)nsn(dot)com>
Subject: Re: Synch Replication
Date: 2009-02-13 10:38:59
Message-ID: 3f0b79eb0902130238g2a46f511jfcdf109f5e6cb74@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Thanks for the comments!

On Fri, Feb 13, 2009 at 5:00 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Fujii Masao escribió:
>
> I noticed two very minor issues while reading your docs:
>
>> This is because WAL files generated in the primary server before this built-in
>> replication starts have to be transferred to the standby server by
>> using file-based log shipping. When <TT
>> CLASS="VARNAME"
>> >archive_mode</TT
>> > is <TT
>> CLASS="LITERAL"
>> >unsent</TT
>> >,
>
> You probably mean "unset" here.

I mean "unsent" here. This is one of valid values of archive_mode
which I changed for synch-rep. Please see the description of
archive_mode in the attached document.

>
>> <TT
>> CLASS="VARNAME"
>> >enable_replication</TT
>> > (<TT
>> CLASS="TYPE"
>> >boolean</TT
>> >)
>
> It has been said that variables that enable/disable features should only
> be named after the feature that they affect, omitting the "enable" verb.
> So in this case it should be set as "replication=off" or
> "replication=on".

Okay, I will rename the parameter like you say. Thanks!

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment Content-Type Size
runtime-config-wal.html text/html 25.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-02-13 10:53:21 Re: Hot Standby: subxid cache changes
Previous Message Peter Eisentraut 2009-02-13 09:41:06 Re: WIP: hooking parser