From: Brian Trammell <bht@cert.org>
To: psql-interfaces@postgresql.org
Subject: DBD::Pg and .pgpass
Date: Wed, 13 Apr 2005 15:04:57 -0400
Message-ID: <e17e509c3f4ead15ab1dffe9d157aadc@cert.org> (raw)
Greetings,
I'm trying to run a Perl script connecting to a PostgreSQL database via
DBI and DBD::Pg as a cron job. I'm already using the .pgpass mechanism
for managing md5 passwords on the client side and would like to use the
same mechanism for connecting from the Perl script. This does not,
however, appear to work. Passing either "" or undef for the password
yields "no password supplied at <script> line <line>".
Though I could (and probably will, as I'm under some time pressure
here) easily hack in a .pgpass parser to the Perl script, this strikes
me as unconscionably inelegant. Is there some magic I'm missing to get
DBD::Pg to play nice with .pgpass, or is this a bug in DBD::Pg (1.21)
or the Postgres (8.0.1) client side itself?
Regards,
Brian
--
Brian H. Trammell / MTS, CERT/NetSA / <bht@cert.org> / 412.268.9748
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: bht@cert.org, psql-interfaces@postgresql.org
Subject: Re: DBD::Pg and .pgpass
In-Reply-To: <e17e509c3f4ead15ab1dffe9d157aadc@cert.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox