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@xxxxxxxxxx EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
