Re: Postgresql logfilename and times in GMT - not EST

Lonni J Friedman <netllama(at)gmail(dot)com> writes:
> On Tue, Dec 4, 2012 at 1:59 PM, Bryan Montgomery <monty(at)english(dot)net> wrote:
>> I changed postgres.conf to have timezone = 'EST' and restarted postgres.
>> However the log file is still 5 hours ahead. What gives? Not the end of the
>> world but a bit annoying.

> you need to set log_timezone . This is a new 'feature' in 9.2 that
> annoyed me as well. I assume that there was a good use case for this.

"New"? log_timezone has been around since 8.3, and it seems like a good
idea to me --- what if you have N sessions each with its own active
timezone setting? Timestamps in the log would be an unreadable mismash
if there weren't a separate log_timezone setting.

What did change in 9.2 is that initdb sets values for timezone and
log_timezone in postgresql.conf, so it's the initdb environment that
will determine what you get in the absence of any manual action.
Before that it was the postmaster's environment.

regards, tom lane