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
The proposed patch would fix this. Password prompts would go to the
terminal. Right now they got to stderr. Does your stderr go to the
dump file?
> 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/o
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
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, ver
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