On Fri, Dec 25, 2009 at 9:56 PM, Andrew Dunstan <and...@dunslane.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
