Re: SR slaves and .pgpass
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-06-07T15:42:05Z
Lists: pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes: > On Mon, Jun 7, 2010 at 5:42 AM, Andrew Dunstan <andrew@dunslane.net> wrote: >> I tried this with a database name of "replication" in the .pgpass file, >> which matches what we need to use in pg_hba.conf, but it failed miserably, >> and only worked when I used a wildcard for the database name in the .pgpass >> file. >> >> If this is expected it needs to be documented more clearly; if not, it's a >> bug. > Yep, this is expected, so we need to improve the doc. Why don't we improve the code, instead? In particular make libpqrcv_connect() do - snprintf(conninfo_repl, sizeof(conninfo_repl), "%s replication=true", conninfo); + snprintf(conninfo_repl, sizeof(conninfo_repl), "%s database=replication replication=true", conninfo); I don't think it's unlikely that someone would try to enter a replication-specific password into ~/.pgpass. regards, tom lane