Re: Problem with log_timezone not being set during early startup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: 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:12:46
Message-ID: 17214.1186243966@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Decibel! 2007-08-04 16:31:08 Re: Problem with log_timezone not being set during early startup
Previous Message Neil Conway 2007-08-04 16:03:12 Re: .NET driver