From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: .ini support for .pgpass |
Date: | 2011-04-06 06:55:04 |
Message-ID: | 1302072904.23164.0.camel@jd-desktop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2011-04-06 at 07:47 +0300, Peter Eisentraut wrote:
> On tis, 2011-04-05 at 16:04 -0700, Joshua D. Drake wrote:
> > Well any libpq app but yes. I actually wonder as to the legitmacy of
> > having both a pgpass and a pg_service. Why not just one of them?
>
> So you can keep passwords in a safer place (= less permissions) than the
> rest of the connection information.
>
> Note also that .pgpass is a mapping from connection information to
> password, whereas pg_service.conf is a mapping from service name to
> connection information. So they operate on different levels.
>
> It's not actually clear from your syntax example what semantics you are
> trying to achieve.
I want to achieve two things:
1. More understandable .pgpass format. Yes, I understand our standard
format, most people won't. Like JoshB said, hard to debug.
2. psql foo, gets me into foo. A macro for connections if you will.
JD
>
>
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2011-04-06 07:10:29 | Re: .ini support for .pgpass |
Previous Message | Pavel Golub | 2011-04-06 06:26:59 | Re: Please review test report form |