From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Willem Herremans <willem(dot)herremans(at)belgacom(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Providing the password to psql from a script |
Date: | 2004-02-14 20:53:28 |
Message-ID: | 20040214205328.GA18329@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Feb 14, 2004 at 05:11:14PM +0100, Willem Herremans wrote:
> I have used the Tcl command
>
> set psqlChannel [open "|psql $dbname" RDWR]
>
> to create a channel that effectively becomes the input/output channel
> for psql. By writing to that channel, SQL statements are sent to psql,
> by reading from that channel, the results are received from psql.
>
> That works fine, as long as psql does not prompt for a password. The
> problem is that psql does not use this channel for prompting for or
> reading the password. Instead, the password is prompted for on, and read
> from, the terminal from which the tcl application was started and that
> is not what I want, because the Tcl application has already received the
> password from the user. It is, as if psql does not use stdout and stdin
> for the password.
Look in the manpage for psql, there are several ways to stop it asking for
passwords, including the PGPASS environment variable, tne .pgpass file and
setting the user as trust in the config.
Any of these will do what you want...
Hope this helps,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> If the Catholic church can survive the printing press, science fiction
> will certainly weather the advent of bookwarez.
> http://craphound.com/ebooksneitherenorbooks.txt - Cory Doctorow
From | Date | Subject | |
---|---|---|---|
Next Message | Michael L. Artz | 2004-02-14 21:35:58 | Pg + perl + apache |
Previous Message | David Helgason | 2004-02-14 18:13:28 | nonblocking libpq large object access? |