BUG #2816: Logfile difference in timestamp between Windows and Linux

From: "Joost Karaaijeveld" <J(dot)Kraaijeveld(at)Askesis(dot)nl>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2816: Logfile difference in timestamp between Windows and Linux
Date: 2006-12-07 13:42:13
Message-ID: 200612071342.kB7DgD0U091842@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 2816
Logged by: Joost Karaaijeveld
Email address: J(dot)Kraaijeveld(at)Askesis(dot)nl
PostgreSQL version: 8.1.5
Operating system: Windows 2000 / Linux Debian Etch
Description: Logfile difference in timestamp between Windows and
Linux
Details:

Printing a timestamp using '%t%' in Windows omits the timezone in the
logfile. In Linux the timezone is printed. Either make the two the same by
default or make it configurable so that the user can make them the same.

I prefer that they both print the timezone by default and do not so if
configured not to do that. I do not think that losing the timezone helps in
interpreting the log files, especially if the PostgrSQL servers are in other
timezones than the applications they serve.

The source code says that the timezone is to long to use. According to
http://msdn2.microsoft.com/en-gb/library/90s5c885(VS.80).aspx
one could use _tzname[0] to get a short versino of the TZ?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Andreen 2006-12-07 16:10:10 8.2 bug: Mixing spi_prepare and spi_exec_query causes postgresql to terminate itself on bad argument types
Previous Message mike godshall 2006-12-07 06:31:39 BUG #2815: Editing / Creating ODBC on Windows fails libintl-2.dll not found