Re: 'replication' keyword on .pgpass (Streaming Replication)

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 'replication' keyword on .pgpass (Streaming Replication)
Date: 2010-01-07 12:34:06
Message-ID: 4B45D4BE.4080309@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao wrote:
> On Thu, Jan 7, 2010 at 5:44 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> Such information are supplied in the parameter 'primary_conninfo' of
>>> recovery.conf. For example;
>>>
>>> primary_conninfo = 'host=192.168.1.50 port=5432 user=foo'
>> So the password can just go there, no?
>
> Yeah, the password can be supplied in primary_conninfo.
>
> primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
>
> Also you can use the environment variable PGPASSWORD.
> Is this enough? I was thinking that some people would
> complain that only the password for replication cannot
> be supplied in .pgpass.

That seems enough to me.

BTW, how do you set up authentication using an SSL certificate? ISTM
that's the way we should be encouraging people to configure
authentication between a master and standby, rather than type a password
to a file.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-01-07 12:37:01 advantage of new vacuum
Previous Message Dave Page 2010-01-07 12:28:37 Re: libpq naming on Win64