Skip site navigation (1) Skip section navigation (2)

Re: timezone GUC

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: timezone GUC
Date: 2011-05-19 16:19:32
Message-ID: 22284.1305821972@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, May 19, 2011 at 12:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> We could do that, but the issue that this code is trying to avoid is
>> that identify_system_timezone can easily add several seconds to the
>> postmaster startup time. So one of the reasons why someone would be
>> putting a timezone setting into postgresql.conf in the first place is
>> to not pay that startup overhead. I'm not thrilled with the idea
>> of defeating that in order to cover the corner case where they remove
>> the setting later.

> Yeah, I'm not thrilled with that either.  However, I'm also not
> thrilled with the existing behavior.  Consistency is the hobgoblin of
> small minds, and also mine.

What would make everybody happy is to find a way of identifying the
system timezone that isn't such a massive, expensive kluge.  Any ideas?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2011-05-19 16:36:20
Subject: Re: Patch by request at pgcon
Previous:From: Andrew DunstanDate: 2011-05-19 16:15:15
Subject: Re: Cannot build docs of 9.1 on Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group