On 2012-12-29 07:23:24 -0500, Peter Eisentraut wrote: > The xlog code uses two different time zone formats at various times. > Here is an example: > > 2012-12-29 07:04:07.338 EST LOG: database system was interrupted; last known > up at 2012-12-29 06:27:02 EST > 2012-12-29 07:04:26.347 EST LOG: last completed transaction was at log time > 2012-12-29 06:34:24.394802-05 > > The second format also does not respect log_timezone, which seems a bit > of a bug. > > It's also not clear why we need three different ways to show > milliseconds within the space of two lines.
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. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
