> Looks like you might also want to use horology-no-DST-before-1970.out.
Done.
> > Should we use our own strtol()?
>
> Mumble. The memcmp fix was all from well-tested parts, but I don't
> think we have a canned test for strtol breakage available. Also,
> I believe that the SunOS strtol lossage has been known and tolerated
> in previous Postgres releases. Since it's not a regression, I'm going
> to change sides and vote with Peter: let's not fix this one now.
Ok.
--
Tatsuo Ishii