> > AIX 3.2.5 supports neither int timezone (even tho configure seems to
> > think it does) nor the Sun/DEC tm struct with tm_gmtoff field. The
> > non-POSIX time handling seems just plain broken. My patches will therefore
> > only affect AIX 3.2.5 and NeXTstep, the other platform without POSIX_TIME.
> > AIX 4.1 supports POSIX_TIME and is therefore not a problem.
I would think that NextStep is at risk of getting dropped from Postgres
support, since it does not have shared memory or, apparently, anything
close to POSIX time support. If there is someone running on NextStep, it
would be good if they would make themselves known so we can see what the
NextStep OS support needs to be (can't believe it _still_ doesn't have
anything like POSIX-compatible time support).
Hey Darren or Frank, you haven't indicated how stale AIX 3.2.5 is. Why
should anyone keep spending time on it when AIX 4.1 is available?
> I compiled it by defining HAVE_INT_TIMEZONE in config.h and leaving
> USE_POSIX_TIME defined. Compiled very nicely. datetime test passed,
> but the abstime, tinterval and horology tests failed. No crashes or core
> dumps, but some "Bad external representation" errors in the log file.
Those might be normal; there are some tests for illegal time strings.
> If you can live with datetime and not abstime, etc..., maybe give this a shot
> until they're fixed.
I think the only fixes already in would help horology, but not abstime
and tinterval. Need more info on problems (but maybe not, if AIX4.1
doesn't show the same problems).
> I personally'll wait for the "Grand Unified Date", ala
> Oracle, but me thinks I'm gonna need a very comfy chair to wait in. :)
Uh, what does a "Grand Unified Date" do which datetime doesn't? (It's OK
to keep the list short :)
- Tom
------------------------------
End of hackers-digest V1 #400
*****************************
