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.
On Feb 27, 2007, at 8:28 AM, Magnus Hagander wrote:
On Mon, Feb 26, 2007 at 09:46:24AM -0500, Bruce Momjian wrote:
Raymond Naseef wrote:
The following bug has been logged online:
Bug reference: 3059
Logged by: Raymond Naseef
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows XP
Description: psql to 'postgres' shortcut
Details:
The shortcut to run psql.exe added to the menus is a great think
to do, but
when the program stops the window closes with no pause or time
delay.
This is a serious issue if the login fails. Sometimes I forget
to start the
server, but I do not know that because I cannot read text in
~0.02 seconds.
BTW, I bet some of your other .bat files have the same issue.
Please run it by doing 1 or other:
1. Putting a "pause" at the end of the batch file.
2. cmd.exe /K "<command line>"
(just note the "" for default user name will make this fail.
Sorry I do
not know how to fix that unless username has no bad-for-cmd
characters in
it, then quotes are not needed)
These solutions are going to make psql very annoying when it does
work
properly.
Indeed. But it *is* also a problem the way it is now (I've noticed
myself a couple of times, but never had the time to fix it)
Perhaps a reasonable thing to do would be to have the shortcut
point to
a .BAT file that does a "pause" only if psql exits with a non-zero
exitcode.
Is this reasonable? Will psql always exit with non-zero when something
like this happen and also importantly, willi t always exit with a zero
exitcode if there is no problem?
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
