Roberts, Jon wrote:
"Roberts, Jon" <Jon.Roberts@xxxxxxxxxxx> writes:
Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
I'm not complaining. I just want to make sure that if I upgrade, it
will fix the problem. An upgrade could possible introduce a new
problem. I also wonder if this is isolated to Win32 because we are
upgrading to Solaris very soon.
Are you able to get your hands on a cheap Linux box (say, convert a
spare desktop) and do some testing on that?
It may also be helpful to test on a Windows machine without a virus
scanner, personal firewall, or other such system-mangling poison.
If you can reproduce the fault in either of those configurations I'm
sure it'd be very informative. Personally (and my opinion isn't worth
much) I'd blame the virus scanner basically by default, because they're
always causing subtle problems and introducing weird quirks. Something
like PostgreSQL really does rely on the OS doing what it says it will,
and virus scanners tend to bend or break the rules.
--
Craig Ringer
