Re: Problem with log_timezone not being set during early startup - Mailing list pgsql-hackers

From Decibel!
Subject Re: Problem with log_timezone not being set during early startup
Date
Msg-id 20070804163108.GG25704@nasby.net
Whole thread Raw
In response to Re: Problem with log_timezone not being set during early startup  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Problem with log_timezone not being set during early startup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Aug 04, 2007 at 12:12:46PM -0400, Tom Lane wrote:
> There's a value judgment involved here: is it better to print timestamps
> in GMT (which the user won't be expecting) than to not print them at all?
> I can see arguments on both sides of that.

As long as it's clear that the times are in GMT I think that's better.

Something else to consider... normally you'd have to have a pretty
serious condition to run into this in normal usage, right? (I doubt
there's many folks that use any debug level, let alone 3) I think that
gives us more flexibility.
--
Decibel!, aka Jim Nasby                        decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Problem with log_timezone not being set during early startup
Next
From: Tom Lane
Date:
Subject: Re: Problem with log_timezone not being set during early startup