| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: keywords on .pgpass |
| Date: | 2009-12-26 01:55:19 |
| Message-ID: | 3f0b79eb0912251755o434941f9he7897302d5a8685f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 25, 2009 at 9:56 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> I don't see the use case for it - .pgpass is for single users, not a whole
> cluster. And it does support wildcards, which takes care of the 'all' case.
> In the case of pg_hba.conf we don't know in advance who will actually be
> connecting. But in the case of .pgpass we do, so the extra utility of
> 'sameuser', 'samerole' and 'samegroup' in this case is not apparent to me.
OK, I might need to focus only on the use of replication, without
being avaricious.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tomas | 2009-12-26 06:24:29 | Re: creating index names automatically? |
| Previous Message | Robert Haas | 2009-12-25 22:27:44 | Re: creating index names automatically? |