Re: Timezone abbreviations - out but not in?

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Timezone abbreviations - out but not in?
Date: 2008-06-10 15:46:16
Message-ID: 937d27e10806100846w1cad52fbrbe7c6785669aa4e4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 10, 2008 at 4:37 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Dave Page" <dpage(at)pgadmin(dot)org> writes:
>> It seems like a bug that we happily output PKST as a timezone (in a
>> 'timestamp with time zone'), but won't accept it back in.
>
> [ shrug... ] The set of timezone abbrevs recognized on input is
> user-configurable, so that situation will always be possible.

Right, but shouldn't we always output something we know we can read
back in (unambiguously), assuming a server with no user defined
abbreviations?

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-06-10 15:49:48 Re: Timezone abbreviations - out but not in?
Previous Message Tom Lane 2008-06-10 15:37:12 Re: Timezone abbreviations - out but not in?