From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
Cc: | Dave Page <dpage(at)postgresql(dot)org>, Pgsql-general(at)postgresql(dot)org |
Subject: | Re: I "might" have found a bug on 8.2.1 win32 |
Date: | 2007-02-02 16:34:25 |
Message-ID: | 200702021634.l12GYPg04457@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tony Caduto wrote:
> Dave Page wrote:
> >
> > What you are saying is that because you don't believe in the pgpass
> > design, you are going to summarily delete them - which I know for
> > absolute sure would *really* annoy some pgAdmin users that I know for
> > a fact have a whole heap of passwords stored in theirs. Doing that
> > would only hurt your products reputation, not mine.
> >
> Dave,
>
> My product is not storing passwords using pgpass without the users
> knowledge.
> If pgAdmin III stored it's own passwords in the registry it would be up
> to the user (as it should be) to use pgpass.
> If they chose to use pgpass, libpq would override the passwords stored
> in the registry anyway, which is what pgAdmin III is doing
> automatically to my application without my or my users consent.
You can disable reading .pgpass by defining the PGPASSFILE environment
variable to point to a non-existant file. This works for all
applications that use libpq.
Here is a funny parable about what happens when you try to please
everybody:
http://www.bartleby.com/17/1/62.html
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. | 2007-02-02 16:36:59 | Re: Postgres SQL Syntax |
Previous Message | Dave Page | 2007-02-02 16:28:09 | Re: I "might" have found a bug on 8.2.1 win32 |