From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Timezone abbreviations - out but not in? |
Date: | 2008-06-10 15:51:52 |
Message-ID: | 20080610155152.GH5198@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page wrote:
> 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?
That makes no sense because it amounts to saying that we can't ever use
any abbreviation. A more useful restriction would be to only output
those that are in the set of input-acceptable abbreviations, but perhaps
this is not easy to implement.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-06-10 15:59:50 | Re: Timezone abbreviations - out but not in? |
Previous Message | Nathan Boley | 2008-06-10 15:51:10 | Re: Proposal - improve eqsel estimates by including histogram bucket numdistinct statistics |