>
> > > 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?
(speaking for Frank) b/c there are companies like ours which have
a LARGE deployment of AIX-3.2.5 boxes (in our case model 220's) and
have absolutely no intention of "upgrading" them to run AIX-4.x.
Especially since we would gain absolutely nothing.... except for a
slower running box. (plus we'd have to port our software to "yet
another platform", since we have alot of custom written code that runs
on these boxes.) Our "upgrade" of an AIX-3.2.5 box would be to
throw it out in favor of something running BSDi or Solaris. But
that will take a long time to do.
Anyway, assuming we favorably work out the problems we're having
with postgres-6.1, we'll end up with a very large deployment
(like over 1000 machines, a mixture of AIX-3.2.5, BSDi-2.1, and
Solaris-2.5.1). We're still doing the testing/modeling/justification
right now. (assuming we dont work it out would force us back to
the drawing board in search of another database that supports all
of our platforms).
Roger.
- --
Roger Florkowski - ANS CO+RE Systems, Inc. - roger@ans.net
------------------------------
