From: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
---|---|
To: | Keary Suska <hierophant(at)pcisys(dot)net>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Reading psql password from stdin |
Date: | 2001-10-15 02:38:35 |
Message-ID: | 3.0.5.32.20011015103835.0086fb50@192.228.128.13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
pg_dump does wait for passwords - version 7.1.x.
But the password prompts end up in the dumpfile.
That is to say, the Username: and/or Password: prompts end up in the
dumpfile and are not displayed on the screen.
Cheerio,
Link.
At 06:19 PM 14-10-2001 -0600, Keary Suska wrote:
>Good, good, very good! being one of the people who steadfastly avoids PGUSER
>and PGPASSWORD for security reasons, it would be nice t be able to do
> $ psql db user < file
>As the docs say you can. Would this change also allow the use of:
> $ pg_dump > dumpfile
>Which doesn't work when prompting for password, but that can be a stdout
>issue.
>
>I would enumerate these issues as the top annoyances with the postgres
>client apps. Although I would place them very low compared to being able to
>alter/remove columns.
>
>Keary Suska
>Esoteritech, Inc.
>"Leveraging Open Source for a better Internet"
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Yeoh | 2001-10-15 02:46:12 | Re: Reading psql password from stdin |
Previous Message | Keary Suska | 2001-10-15 00:19:37 | Re: Reading psql password from stdin |