Hi all, my next TODO item for the Win32 port was to try to bring all the regression tests up.
Pleased to report that, with a great deal of hackage + kludges (which I hope to refine and submit as patches for review over the next couple weeks), all but 10 tests pass! 7 of these fail pretty much *only* due to localtime returning NULL for pre-1970 dates, specifically: date, timestamp, timestampz, abstime, tinterval, horology, arrays. To resolve this, seems like there are 3 solutions: a) Provide "post-1970-only" versions of the expected regression test output, for use under win32 b) Remove pre-1970 dates from *all* regression test files c) Code up "pg_localtime" for win32 None of these are appealing, particularly b). Any better ideas? With this issue aside, that leaves three tests remaining for examination: join, rules and stats. The regression diffs are attached. The join and rules failures don't look material, AFAICS, as the right rows are returned, just not necessarily in the expected order... is this an issue? Is the order mandated in these cases. Again, afaIcs, it isn't, but strictly I'm out of my depth here. This leaves the stats test as possibly the only real remaining failure. An analysis (collector not running?) based on the diff would be appreciated, as well as pointers to which lines of code/functions one would expect to see invoked if this test was running correctly, to help debugging. Cheers, Claudio --- Certain disclaimers and policies apply to all email sent from Memetrics. For the full text of these disclaimers and policies see <a href="http://www.memetrics.com/emailpolicy.html";>http://www.memetrics.com/em ailpolicy.html</a>
regression.diffs
Description: Binary data
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
