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

From Tom Lane
Subject Re: Problem with log_timezone not being set during early startup
Date
Msg-id 17214.1186243966@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problem with log_timezone not being set during early startup  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Problem with log_timezone not being set during early startup  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Any way to tweak this place and have it log in GMT instead, when
> log_timezone is NULL?

I think this is just a variant of my #2.  The main risk factor IMHO
is that the first call is going to invoke tzload() for the GMT zone
(pgtz does not seem to special-case GMT in any meaningful way),
and it's not entirely clear how much infrastructure has to be up
before that would work.  It's probably all right, seeing that we
won't get here until GUC has set log_line_prefix to something
nondefault, but I haven't tried it.

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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Neil Conway
Date:
Subject: Re: .NET driver
Next
From: Decibel!
Date:
Subject: Re: Problem with log_timezone not being set during early startup