time_t problem with postgresql

[Alan Barrett <apb%cequrux.com@localhost>]

On Wed, 11 Mar 2009, Daniel Carosone wrote:
> My guess, repeated from last time[sic]: time_t is being written to
> disk, and has changed size. This is causing fallout elsewhere, as
> later fields are being read at the wrong offsets, giving odd results
> like above. 

Yes, postgresql writes (used to write) time_t to disk,
and gets confused when sizeof(time_t) changes.  See
<https://projects.commandprompt.com/public/pgsql/changeset/27784> for
the fix.  I don't know which versions of postgresql include this fix.

--apb (Alan Barrett)