Re: inconsistent time zone formats in log

On 30/12/12 05:24, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>> On 2012-12-29 07:23:24 -0500, Peter Eisentraut wrote:
>>> The xlog code uses two different time zone formats at various times.
>> One is a pg_time_t (stored in pg_control/ControlFileData), the other is
>> a TimestampTz. Those have completely different code paths for being
>> printed (pg_strftime vs EncodeDateTime) ...
>> I don't want to say its impossible or shouldn't be fixed, just that its
>> not trivial to do so.
> Presumably, any fix would involve changing one or the other of those
> so that we use only one timestamp representation in xlog. I'm not
> terribly convinced that it's worth worrying about though. Do we need
> microsecond precision in the database start/stop times?
>
> regards, tom lane
>
>
If I saw an inconsistency like that in a production log, while chasing
an apparent case of corruption, I would tend to think that the
differences in time might be giving me a hint. Knowing my luck, that
will happen to me in a couple of years, after I've forgotten this email
tread!

Cheers,
Gavin