Marvin Bellamy <marvin(dot)bellamy(at)innovision(dot)com> writes:
> I've been treating the timestamp as an integer, not a double. What's a
> good way to deal with double/float byte ordering when reading/writing
> data from Windows applications?
Pretend it's an integer for long enough to byte-swap it the same way as
you'd do for an integer of the same size. (IIRC this is exactly how the
backend does it, too.)
regards, tom lane