Re: WTF? 9.2.4 Logs have the wrong day of the week?

From: Christian Ullrich <chris(at)chrullrich(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: WTF? 9.2.4 Logs have the wrong day of the week?
Date: 2013-08-16 13:55:53
Message-ID: kulb12$q8i$1@ger.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

* Scott Whitney wrote:

> Everything you need to see is right here:
>
> [root@<serverNameRemoved> pg_log]# ls -lrt
> total 5924
> -rw------- 1 postgres postgres 708669 Aug 8 18:59 postgresql-Thu.log
> -rw------- 1 postgres postgres 669505 Aug 9 18:59 postgresql-Fri.log
> -rw------- 1 postgres postgres 666603 Aug 10 18:56 postgresql-Sat.log
> -rw------- 1 postgres postgres 559716 Aug 11 18:59 postgresql-Sun.log
> -rw------- 1 postgres postgres 626143 Aug 12 18:56 postgresql-Mon.log
> -rw------- 1 postgres postgres 2065282 Aug 13 18:24 postgresql-Tue.log
> -rw------- 1 postgres postgres 755099 Aug 13 19:22 postgresql-Wed.log
>
> [root@<serverNameRemoved> pg_log]# date
> Tue Aug 13 19:23:53 CDT 2013

log_timezone is set to UTC, which is normally six hours ahead of
Chicago, but does not observe DST, so currently it is five hours ahead.
18:24 plus five is still the same day, 19:22 plus five is the next day.

Quoting the docs:

log_timezone (string)

Sets the time zone used for timestamps written in the server log. Unlike
TimeZone, this value is cluster-wide, so that all sessions will report
timestamps consistently. The built-in default is GMT, but that is
typically overridden in postgresql.conf; initdb will install a setting
there corresponding to its system environment.

--
Christian

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Dzmitry 2013-08-19 08:07:12 postgres crashes on insert in 40 different threads
Previous Message Natalie Wenz 2013-08-14 14:52:08 Re: vacuum freeze performance, wraparound issues