pgpass replacement?

[anarchodin]

Connecting to a database using environment variables and pgpass, I now see a deprecation notice. The notice suggests using a function to return a password, which is fair enough. However, it seems to me like that requires me to reimplement the libpq environment parsing to work, as that function gets no arguments, and the pgpass module doesn't read the environment. Is there an actually simple way to do this?

Also, one instance of the word function gets spelled 'funciton' in the notice.

[brianc]

Hmmn sorry I'm not entiiiirely understanding your question. If your password is in the environment variable PGPASSWORD it will automatically be read & used. If it's in a pgpass file, you can use the pgPass module directly.

Oh....I see the password callback method isn't called with the connection parameters...and you don't have convenient access to them & pgPass library needs them. Well - how about I modify things to pass the parameters to the password callback? Would that work?

Also, ty for the heads up wrt the function misspelling. I'll get that fixed as well. 😄

[brianc]

@anarchodin #3602 should fix this for you! The reason I want to remove explicit dependency on pgpass is its not commonly used and I want to keep 3rd party dependencies to an absolute minimum so this makes it an optional thing & lets pg itself be extensible w/o having to ship as many modules I don't control.

[anarchodin]

Thank you, that should cover it nicely. I found the reasoning through the commit adding the notice, and it absolutely makes sense.

I find using .pgpass convenient for development environments, but evidently I'm in a minority on that.