From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
Cc: | 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 04:00:31 |
Message-ID: | 200110150400.f9F40Vu21516@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Oops, sorry, I see my question was answered.
---------------------------------------------------------------------------
> 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"
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | xavier lhomme | 2001-10-15 07:06:59 | store a 3D path |
Previous Message | Bruce Momjian | 2001-10-15 04:00:03 | Re: Reading psql password from stdin |