Re: Trouble with 64-bit time_t on 6.0_STABLE

[christos%astron.com@localhost (Christos Zoulas)]

In article <20121019144747.GC15349%mail.duskware.de@localhost>,
Martin Husemann  <martin%duskware.de@localhost> wrote:
>On Fri, Oct 19, 2012 at 09:36:13PM +0700, Pongthep Kulkrisada wrote:
>> But what if this kind of problem comes up?
>
>It is better to define on-disk structure layout with fixed size types
>only (like uint32_t or uint64_t).

Absolutely! You cannot depend on opaque types to retain their size and
structure over time. You should convert the structures that define the
on-disk format to use fixed size (and meaning types) as described above.
But programs make this mistake a lot (mercurial, postgress) but when
things change, they fix it.

christos