Dave Page wrote: > On Tue, Jun 10, 2008 at 4:37 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > > "Dave Page" <[EMAIL PROTECTED]> 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 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
