Search Postgresql Archives

Re: I "might" have found a bug on 8.2.1 win32

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dave Page wrote:

I must Be missing the point - why should I work something out with your app for using a documented feature of libpq in pgAdmin?

Dave,
The whole point is pgAdmin III is storing the password in the pgpass file which is global for every single application that uses it, don't you see the problem? It's clear as crystal!!!! pgAdmin III should be storing the password on win32 in the registry like every other win32 program does, or in a ini file, it's the accepted way to do that sort of thing on win32. It just is, and the way you are doing it is not the way it should be done in the win32 world. I was just asking that we work together to find a way our applications would not affect each other, and currently pgAdmin III is the clear violator by using a global feature of libpq to store passwords for its own use without regard for other applications that may be using libpq.

I don't think the pgpass file was intended to be used as a password storage method for pgAdmin III, it was meant as a way to allow psql and other command line programs to be easily used from scripts where it would be detrimental to have a password prompt pop up during a scheduled run or maybe I am wrong and it was created just for the use of pgAdmin III but
that does not really matter.

I am sorry, but I believe the way pgAdmin III is using the pgpass file is TOTALLY WRONG, sorry but it just is.

It's global to every single app that uses libpq on the PC, I just don't understand why you don't get it.

The way you make it sound is like pgAdmin III does not want to play nice with other applications, and I can do that to. I don't want to delete the pgpass file, but I will so my application gets the same rights as pgAdmin III. I have users who set their test servers to trust and why should I make them store a password when they don't need to? That's what I would have to do, force the user to enter some form of password, so it's not blank or force them to store a password even if the server is set for trust access.

Sorry in advance if you don't like what I have to say, but sometimes you can be very stubborn and one way or the highway!!!

Later,

--
Tony Caduto
AM Software Design
http://www.amsoftwaredesign.com
Home of PG Lightning Admin for Postgresql
Your best bet for Postgresql Administration


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux