On Jul 6, 2011, at 9:24 AM, Alexey Klyukin wrote: > So, I'd think there are 2 reasonable approaches to storing the > timezone part: > > 1. Store the timezone abbreviation (i.e. 'EST' along w/ the timestamp > data). > 2. Assign OID to each of the timezones and store it w/ the timestamp. > > The first option seem to avoid the necessity of creating a new system > catalog for timezone information and the burden of updating it, > because current implementation is already capable of translating > abbreviations to useful timezone information. The question is, whether > just a TZ abbreviation is sufficient to uniquely identify the timezone > and get the offset and DST rules. If it's not sufficient, how > conflicting TZ short names are handled in the current code (i.e. 'AT > TIME ZONE ...')?
It's not enough. See the timezone_abbreviations setting. -- Jim C. Nasby, Database Architect j...@nasby.net 512.569.9461 (cell) http://jim.nasby.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
