| 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:46:12 |
| Message-ID: | 3.0.5.32.20011015104612.00855650@192.228.128.13 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Correction:
The password promps only end up in the dumpfile for version 6.5.
pg_dump does wait and prompt for passwords if you use -u for version 7.1.x.
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 | Bruce Momjian | 2001-10-15 04:00:03 | Re: Reading psql password from stdin |
| Previous Message | Lincoln Yeoh | 2001-10-15 02:38:35 | Re: Reading psql password from stdin |