On Wed, Jan 6, 2010 at 15:02, Alvaro Herrera <alvherre@commandprompt.com> wrote:
> Fujii Masao escribió:
>> On Sat, Dec 26, 2009 at 10:55 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> > On Fri, Dec 25, 2009 at 9:56 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
>> >> I don't see the use case for it - .pgpass is for single users, not a whole
>> >> cluster. And it does support wildcards, which takes care of the 'all' case.
>> >> In the case of pg_hba.conf we don't know in advance who will actually be
>> >> connecting. But in the case of .pgpass we do, so the extra utility of
>> >> 'sameuser', 'samerole' and 'samegroup' in this case is not apparent to me.
>> >
>> > OK, I might need to focus only on the use of replication, without
>> > being avaricious.
>>
>> The attached patch supports new keyword 'replication' on .pgpass file.
>> This keyword is used to specify the password for the standby server to
>> connect to the primary server.
>
> Would it make more sense to have a separate password file for the
> replication stuff? Say .pgreplicationpass or whatever.
I haven't read up on the rest of the patch, but where do we put the
rest of the information about the replication master? Like which IP
and port to connect to? Perhaps it could/should go there?
-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/