| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | 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 09:13:41 |
| Message-ID: | 3f0b79eb1001070113g1bd24546v1a38dbe48375007@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2010-01-07 09:19:29 | Re: true serializability and predicate locking |
| Previous Message | Joshua Tolley | 2010-01-07 09:09:51 | Hot standby documentation |