On Fri, Jan 19, 2001 at 09:19:34PM +0900, Yutaka tanida wrote:
> > Are you still attempting to fix this problem? Please do not interpret
> > this as a request. I will understand if you do not want or have time to
> > continue with this effort. I just need to know whether or not I should
> > start to debug myself.
> Today, I'm working on this and finally create a patch against cygwin
> 1.1.7 . This patch fixes PostgreSQL's problem , but attatched C program
> doesn't work correctly.
Thanks for the status update. Do you think that you will be able to
find a solution that fixes the PostgreSQL problem *without* breaking
Originally you thought that the problem was in cygipc. Have you
concluded that the problem is actually in Cygwin?
BTW, this problem is becoming a really nuisance. I was running many
regression tests sequentially last night. If I forget to kill postmaster
from the previous test, then the next regression test would fail because
the regression database "already existed." When I do remember to kill
postmaster it takes between 5 - 10 kills to really kill it.
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
In response to
pgsql-ports by date
|Next:||From: Yutaka tanida||Date: 2001-01-23 04:11:13|
|Subject: Re: (Cygwin) postmaster shutdown problem|
|Previous:||From: Jason Tishler||Date: 2001-01-22 05:56:37|
|Subject: Re: [PATCH]: Building PostgreSQL 7.0.2 on Cygwin 1.1.4 (Take 2)|