Re: BUG #3059: psql to 'postgres' shortcut
| От | Magnus Hagander |
|---|---|
| Тема | Re: BUG #3059: psql to 'postgres' shortcut |
| Дата | |
| Msg-id | 20070430102611.GB13100@svr2.hagander.net обсуждение исходный текст |
| Ответ на | Re: BUG #3059: psql to 'postgres' shortcut (Bruce Momjian <bruce@momjian.us>) |
| Список | pgsql-bugs |
On Tue, Feb 27, 2007 at 02:08:38PM -0500, Bruce Momjian wrote: > Magnus Hagander wrote: > > On Tue, Feb 27, 2007 at 09:06:17AM -0500, Phil Frost wrote: > > > Hrm...I haven't used windows for a while now, but isn't there an > > > option on all shortcuts to command-line programs to make the shell > > > pause on exit? It is something like, right click on shortcut, select > > > 'properties', uncheck 'close shell on exit'. It would seem this would > > > solve the problem of not being able to see errors, while also not > > > adding a pause for programs which execute psql.bat directly. > > > > Yes, that is exactly the point -it would be very annoying in all other > > cases, as Bruce pointed out. > > > > I guess another option would be to add a commandline option to psql to > > pause on error, but I don't think that's going to fly ;-) > > Notice EXIT_BADCONN. So, what if we call psql from a batch file, and > check for a '2' exit status, and then issue a pause for only that case? I have applied a fix for the 8.3 pginstaller that does just this. Will be in the next snapshot/release. //Magnus
В списке pgsql-bugs по дате отправления: