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!
McC
Tom Lane wrote:
Sean McCune <[EMAIL PROTECTED]> writes:
I have not run into this problem under Linux before, but that doesn't
mean anything. This application running under cygwin is more heavy duty
than what I've run on Linux. So we don't know if its a general postgres
bug or something that's only occurring on cygwin.
We have heard of similar things under cygwin, so I'd suppose it's a
cygwin bug. Postgres does not do its own timekeeping --- it believes
whatever time(2) and gettimeofday(2) tell it --- so it's definitely an
OS-level problem.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
