Re: Why do we have a database specification in .pgpass?

Peter Eisentraut wrote:
> 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.

Agreed, done.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 70d9202..a911c50 100644
*** a/doc/src/sgml/libpq.sgml
--- b/doc/src/sgml/libpq.sgml
*************** myEventProc(PGEventId evtId, void *evtIn
*** 6331,6336 ****
--- 6331,6338 ----
     or the default socket directory) connections coming from the local
     machine. In a standby server, a database name of <literal>replication</>
     matches streaming replication connections made to the master server.
+    The <literal>database</> field is of limited usefulness because
+    users have the same password for all databases in the same cluster.
    </para>

    <para>