I'm not familiar with dbexperts version, but I think that's a native Win32 version, which shoots down cygwin as the culprit and starts pointing the finger at Windows. That figures.
On Fri, 2004-06-25 at 06:39, Richard Huxton wrote: > Sean McCune wrote: > > OK, I'll look at it from the cygwin end. Its interesting that > > restarting postgres clears it. Although, I guess this could be a > > problem in the cygwin DLL. Thanks for the very quick response! > > Just for the record, I had a client report the same thing a couple of > days ago with (iirc) the dbexperts version. Restarting PG fixed it there > too. -- Sean McCune Red Hand Software, Inc. [EMAIL PROTECTED] Land: 724-224-7323 Cell: 724-316-5456 Fax: 412-291-1520 ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
