From: | Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Horák Daniel <horak(at)sit(dot)plzen-city(dot)cz>, pgsql-ports(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: Cygwin PostgreSQL CVS Patch |
Date: | 2001-01-16 03:56:50 |
Message-ID: | 20010115225650.A1748@dothill.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-ports |
Tom,
On Mon, Jan 15, 2001 at 05:23:20PM -0500, Tom Lane wrote:
> Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com> writes:
> > I've already tested the no postmaster case. Please be more explicit
> > regarding "connecting to a nonexistent socket" and etc. I'm afraid that
> > if I guess then I'll miss something.
>
> The cases I was thinking of were (a) no socket file (normal case if no
> postmaster) and
Case a behaves correctly.
> (b) socket file present but no postmaster attached ---
> you can get that by kill -9'ing the postmaster ...
Unfortunately, case b causes psql to hang. Using gdb, I was able to
trace that psql hangs calling select() in pqWait() (i.e.,
src/interfaces/libpq/fe-misc.c line 739).
I'm pretty sure that this is Cygwin bug. I will try to formulate
a minimal test for submission to the Cygwin list but I'm not that
experienced with sockets. Would anyone like to assist me with this
endeavor?
I will hold off submitting the patch until this is fixed.
Thanks,
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason(dot)Tishler(at)dothill(dot)com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Tishler | 2001-01-16 04:37:55 | Cygwin PostgreSQL Regression Test Problems |
Previous Message | Tom Lane | 2001-01-15 22:23:20 | Re: Cygwin PostgreSQL CVS Patch |