Thread: keywords on .pgpass

Hi,

pg_hba.conf accepts some keywords like 'all', 'sameuser' and so on.
Likewise, I'd like to support the same keywords for .pgpass file.
Thought?

In Streaming Replication, new keyword 'replication' has been introduced
into pg_hba.conf to authenticate the standby server. If my proposal will
have been accepted, I'll also add the 'replication' keyword into .pgpass
file. This keyword is required to specify the password which the standby
uses since the connection for replication doesn't correspond to the specific
database.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Fujii Masao wrote:
> Hi,
>
> pg_hba.conf accepts some keywords like 'all', 'sameuser' and so on.
> Likewise, I'd like to support the same keywords for .pgpass file.
> Thought?
>
>
>   

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.

cheers

andrew

On Fri, Dec 25, 2009 at 9:56 PM, Andrew Dunstan <andrew@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