[EMAIL PROTECTED] wrote: > On Thu, 28 Oct 2004, Bruce Momjian wrote: > > > Date: Thu, 28 Oct 2004 19:58:56 -0400 (EDT) > > From: Bruce Momjian <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Cc: Tom Lane <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > > Subject: Re: [HACKERS] Unixware 714 pthreads > > > > [EMAIL PROTECTED] wrote: > > > I agree with all that you say Tom, I'm just asking for some help to debug > > > this, Now that Larry is a litle off the list, I'm feeling really lonely on > > > UW. > > > SCO won't do anything until I come up with a test program that fails. All > > > my tries did work until then. > > > > > > I use other threaded progs like postfix or bind that nether fail. > > > > > > I'm really at lost. Would you/someone help me? > > > > The problem is that we are then spending our time debugging Unixware > > problems rather than focusing on our database software. I think this is > > why few have offered assistance. > > > > > I understand your concerns, OTOH you all spend quite a lot of time > debugging windows... > > Anyway, the little program attached does more or less what postgresql does > in term of sigaction and setitimer (Yes, unixware DOES have posix signals) > and works like a charm wether compiled with or without pthreads.
That work is done by people who care about the Win32 port and plan to use it, just like you are debugging Unixware because you use it. We don't expect non-Win32 users to fix Win32 problems and we don't expect non-Unixware people to fix Unixware problems. Each platform's users have to track down its own bugs for us to work efficiently. Also, we haven't spent much time tracking down Win32 bugs but more figuring out how to use the Win32 API. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
