Re: Comments to Synchronous replication patch v3

From: "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "Dickson S(dot) Guedes" <guediz(at)gmail(dot)com>, "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Comments to Synchronous replication patch v3
Date: 2008-11-25 16:40:41
Message-ID: 3f0b79eb0811250840i544e6be0t86db5ce1b8da0b8e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 26, 2008 at 12:23 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Fujii Masao escribió:
>> On Tue, Nov 25, 2008 at 10:57 PM, Alvaro Herrera
>> <alvherre(at)commandprompt(dot)com> wrote:
>> > Dickson S. Guedes escribió:
>> >> Fujii Masao escreveu:
>> >>> (...)
>> >>>> Even if we need to have the database in real, I'd like to use another
>> >>>> name for it. The name 'walsender' seems to be an internal module name
>> >>>> but it should be a feature name (ex. 'replication').
>> >>>>
>> >>>
>> >>> Agreed. The name 'replication' is more suitable, I also think.
>> >>> Any other ideas?
>> >>
>> >> 'walsender' should be a schema in the 'replication' database. Other
>> >> modules, in replication feature, could be placed there too.
>> >
>> > Hmm, what is this database there for?
>>
>> It's for authentication for replication. This was discussed before.
>> Please see the following thread and feel free to comment.
>> http://archives.postgresql.org/pgsql-hackers/2008-11/msg00187.php
>
> Hmm ... I think this means that the suggestion by Dickson does not make
> much sense, right?

Oh, I'm sorry!

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2008-11-25 16:45:40 Re: TODO item: adding VERBOSE option to CLUSTER [with patch]
Previous Message Tom Lane 2008-11-25 15:50:09 Re: Brittleness in regression test setup