| From: | Kenneth Marshall <ktm(at)rice(dot)edu> |
|---|---|
| To: | Dennis Bj??rklund <db(at)zigo(dot)dhs(dot)org> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why do we have a database specification in .pgpass? |
| Date: | 2010-10-14 13:46:16 |
| Message-ID: | 20101014134616.GF14946@aart.is.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(at)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-14 13:50:15 | Re: SQL command to edit postgresql.conf, with comments |
| Previous Message | Kevin Grittner | 2010-10-14 12:55:22 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |