| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| 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 09:21:10 |
| Message-ID: | 3f0b79eb1001070121p55c53131uc543e1c681294bd9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Barbier | 2010-01-07 09:28:33 | Re: Serializable Isolation without blocking |
| Previous Message | Albe Laurenz | 2010-01-07 09:19:29 | Re: true serializability and predicate locking |