Re: [HACKERS] inconsistent time zone formats in log

2012-12-29 Thread Gavin Flower
On 30/12/12 05:24, Tom Lane wrote: Andres Freund 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 diff

Re: [HACKERS] inconsistent time zone formats in log

2012-12-29 Thread Tom Lane
Andres Freund 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 > p

Re: [HACKERS] inconsistent time zone formats in log

2012-12-29 Thread Andres Freund
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: l

[HACKERS] inconsistent time zone formats in log

2012-12-29 Thread Peter Eisentraut
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.39