Horton

Thread

  1. Why do we have a database specification in .pgpass?

    Bruce Momjian <bruce@momjian.us> — 2010-10-13T18:32:22Z

    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.

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

  + It's impossible for everything to be true. +

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

    Andrew Dunstan <andrew@dunslane.net> — 2010-10-14T01:39:04Z

    
On 10/13/2010 02:32 PM, 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.

If you use wildcards for some of the other params it could well be useful.

cheers

andrew

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

    Alvaro Herrera <alvherre@commandprompt.com> — 2010-10-14T02:15:11Z

    Excerpts from Bruce Momjian's message of mié oct 13 15:32:22 -0300 2010:
> 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.

I think when I wrote it, I was hoping that the db_user_namespace thing
would be changed into a real per-database user implementation.  That
would have meant having different passwords depending on the database.


-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

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

    Dennis Björklund <db@zigo.dhs.org> — 2010-10-14T04:09:35Z

    > 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.

There is the GUC parameter db_user_namespace. Just for that you could
probably  use dennis@foo as username instead, so maybe it's not the
purpose. But I can't think of any other reason.

/Dennis

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

    Pavel Golub <pavel@microolap.com> — 2010-10-14T06:29:25Z

    Hello, Bruce.

You wrote:

BM> We have a database specification in .pgpass:

BM>         hostname:port:database:username:password

BM> What is the purpose of 'database' since username/password combinations
BM> are global, not per database?  I would like to documents its purpose.

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

BM>   + It's impossible for everything to be true. +


For future use?

-- 
With best wishes,
 Pavel                          mailto:pavel@gf.microolap.com

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

    Kenneth Marshall <ktm@rice.edu> — 2010-10-14T13:46:16Z

    On Thu, Oct 14, 2010 at 06:09:35AM +0200, Dennis Bj??rklund 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.
> 
> There is the GUC parameter db_user_namespace. Just for that you could
> probably  use dennis@foo as username instead, so maybe it's not the
> purpose. But I can't think of any other reason.
> 
> /Dennis
> 

This will allow the same user to save and use automatically different
passwords for each separate database.

Cheers,
Ken

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

    Peter Eisentraut <peter_e@gmx.net> — 2010-10-16T10:23:12Z

    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.

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

    Bruce Momjian <bruce@momjian.us> — 2010-10-21T21:46:50Z

    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. +