Re: 'replication' keyword on .pgpass (Streaming Replication)
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, Alvaro Herrera <alvherre@commandprompt.com>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-01-07T12:50:12Z
Lists: pgsql-hackers
On Thu, Jan 7, 2010 at 13:34, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > Fujii Masao wrote: >> On Thu, Jan 7, 2010 at 5:44 PM, Magnus Hagander <magnus@hagander.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. Connectoin parameters: sslcert, sslkey and sslrootcert in most cases. Or just put the key in ~/.postgresql/postgresql.key. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/