Re: Why do we have a database specification in .pgpass? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Why do we have a database specification in .pgpass?
Date
Msg-id 1287224592.5599.5.camel@vanquo.pezone.net
Whole thread Raw
In response to Why do we have a database specification in .pgpass?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Why do we have a database specification in .pgpass?
List pgsql-hackers
On ons, 2010-10-13 at 14:32 -0400, Bruce Momjian wrote:
> We have a database specification in .pgpass:
> 
>         hostname:port:database:username:password
> 
> What is the purpose of 'database' since username/password combinations
> are global, not per database?  I would like to documents its purpose.

As a side note, the thing at the other end of a connection is not
necessarily a PostgreSQL server.  It could be a connection pool proxy.
I don't know if any implementatation could make use of the database
field at the moment, but it should be kept in mind.

That said, it would probably be good to document that the database field
is currently only useful in certain limited circumstances.



pgsql-hackers by date:

Previous
From: fazool mein
Date:
Subject: Timeline in the light of Synchronous replication
Next
From: Peter Eisentraut
Date:
Subject: all keyword for pg_hba.conf host column