From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:48:12 |
Message-ID: | 9837222c1001070448w327108b4tee6920192b85018@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 7, 2010 at 10:21, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Thu, Jan 7, 2010 at 5:46 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> However, wouldn't it make more logical sense to replace "host/hostssl"
>> with "replication/replicationssl" rather than overload the database
>> field?
>
> Seems good. How about the following formats?
>
> replication user CIDR-address auth-method [auth-options]
> replicationssl user CIDR-address auth-method [auth-options]
> replication user IP-address IP-mask auth-method [auth-options]
> replicationssl user IP-address IP-mask auth-method [auth-options]
>
> Note that "database" field has been removed since it's useless
> for replication.
Hm, no, I think I withdraw my comment about pg_hba.conf. It seems
better to overload the database name here. I'm not particularly keen
on yet another different set of columns, which is what happens when
you remove the database field.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-01-07 12:50:12 | Re: 'replication' keyword on .pgpass (Streaming Replication) |
Previous Message | Heikki Linnakangas | 2010-01-07 12:44:43 | Re: 'replication' keyword on .pgpass (Streaming Replication) |