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 20070804165008.GI25704@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
List pgsql-hackers
On Sat, Aug 04, 2007 at 12:46:32PM -0400, Tom Lane wrote:
> Decibel! <decibel@decibel.org> writes:
> > 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.
>
> Yeah.  This whole issue will really only affect developers, except for
> cases where startup fails completely.

And when startup fails completely, you're far less likely to care about
timezone.

Perhaps if we don't have log_timezone set yet we could output something
such as 'LOCALTIME' so that it was obvious. Or maybe output whatever $TZ
is set to?
--
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: Andrew Dunstan
Date:
Subject: Re: .NET driver