| From: | Decibel! <decibel(at)decibel(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Problem with log_timezone not being set during early startup |
| Date: | 2007-08-04 16:50:08 |
| Message-ID: | 20070804165008.GI25704@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Aug 04, 2007 at 12:46:32PM -0400, Tom Lane wrote:
> Decibel! <decibel(at)decibel(dot)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(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-08-04 17:25:48 | Re: .NET driver |
| Previous Message | Tom Lane | 2007-08-04 16:46:32 | Re: Problem with log_timezone not being set during early startup |