From: | Raymond Naseef <raymondnaseef(at)yahoo(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Phil Frost <phil(at)macprofessionals(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3059: psql to 'postgres' shortcut |
Date: | 2007-02-28 00:25:38 |
Message-ID: | 339874.83662.qm@web53608.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Dear Team,
I checked the shortcut and was unable to find any note about "close on exit" or anything like that. The .bat method sounds wonderful, and I would appreciate such a change to make the product a little more responsive.
Thank you for your consideration and time,
Raymond Naseef
P.S. I apologize if my email were not being sent properly. I will pay close attention to this going forward.
----- Original Message ----
From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Phil Frost <phil(at)macprofessionals(dot)com>; Raymond Naseef <raymondnaseef(at)yahoo(dot)com>; pgsql-bugs(at)postgresql(dot)org
Sent: Tuesday, February 27, 2007 2:08:38 PM
Subject: Re: [BUGS] BUG #3059: psql to 'postgres' shortcut
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 ;-)
I just ran a test on Unix and found psql exits with '2' if the password
fails. In fact, looking at the psql sources I see:
#ifndef EXIT_SUCCESS
#define EXIT_SUCCESS 0
#endif
#ifndef EXIT_FAILURE
#define EXIT_FAILURE 1
#endif
#define EXIT_BADCONN 2
#define EXIT_USER 3
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?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
____________________________________________________________________________________
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
From | Date | Subject | |
---|---|---|---|
Next Message | Akio Iwaasa | 2007-02-28 03:02:25 | BUG #3086: DBMirror's error (SERIAL attribute) |
Previous Message | postgres | 2007-02-27 22:55:19 | BUG #3085: Performance BUG |