From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John Summerfield <pgtest(at)ami(dot)com(dot)au> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: psql in 7.2devel loops |
Date: | 2002-02-01 19:43:23 |
Message-ID: | 11947.1012592603@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
John Summerfield <pgtest(at)ami(dot)com(dot)au> writes:
> It used to be the case that psql could [ read a password from stdin ]
> Now, it writes a password prompt (successfully in my case) and tries to
> read the password (presumably from the tty) which fails.
This was a deliberate change. I wasn't that happy with it myself,
but I was outvoted. You're gonna have to find another way; sorry.
I think "expect" was mentioned as one way of feeding passwords to
programs that will only talk to a tty. On the whole, though, you'd
be better off not embedding passwords in scripts in the first place.
Consider rethinking your PG authorization strategy. (On Linux,
at least, "ident" now works nicely across Unix sockets.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-02-01 19:45:36 | Re: Queries Errors |
Previous Message | Grant Johnson | 2002-02-01 19:24:48 | Re: initdb problems |