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/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" > > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
