Re: timezone GUC

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: timezone GUC
Date: 2011-09-06 20:46:29
Message-ID: 21129.1315341989@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Sep 6, 2011 at 3:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> Was this dealt with?

>> Yes, as much as I think is reasonable anyway. See
>> commit e05b866447899211a0c2df31bf0671faac4fc3e5.

> I am (and, I think, Alvaro is also) of the opinion that the behavior
> here is still not really right.

I don't see a practical way to do better unless we can find a less
horridly inefficient way of implementing identify_system_timezone().
Unfortunately, it's unlikely that there is one, even if you're willing
to make the simplifying assumption that the system timezone is based
on some entry in the Olson database.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marti Raudsepp 2011-09-06 20:52:18 [PATCH] Log crashed backend's query (activity string)
Previous Message Tom Lane 2011-09-06 20:40:10 Re: [v9.1] sepgsql - userspace access vector cache