|
|
|
|
|
|
The following time zone names are recognized by Vertica as valid settings for the SQL time zone (the TIMEZONE run-time parameter).
The names listed here are for convenience only and may be out of date. Refer to the Sources for Time Zone and Daylight Saving Time Data page for precise information.
These names are not the same as the names shown in Time Zone Abbreviations For Input, which are recognized by Vertica in date/time input values. The TIMEZONE names shown below imply a local daylight-savings time rule, where date/time input names represent a fixed offset from 
UTC.
In many cases there are several equivalent names for the same zone. These are listed on the same line. The table is primarily sorted by the name of the principal city of the zone.
Time Zone |
CET |
EET |
Factory |
GMT GMT+0 GMT-0 GMT0 Greenwich Etc/GMT Etc/GMT+0 Etc/GMT-0 Etc/GMT0 Etc/Greenwich |
MET |
UCT Etc/UCT |
UTC Universal Zulu Etc/UTC Etc/Universal Etc/Zulu |
WET |
In addition to the names listed in the table, Vertica will accept time zone names of the form STDoffset or STDoffsetDST, where STD is a zone abbreviation, offset is a numeric offset in hours west from UTC, and DST is an optional daylight-savings zone abbreviation, assumed to stand for one hour ahead of the given offset. For example, if EST5EDT were not already a recognized zone name, it would be accepted and would be functionally equivalent to USA East Coast time. When a daylight-savings zone name is present, it is assumed to be used according to USA time zone rules, so this feature is of limited use outside North America. One should also be wary that this provision can lead to silently accepting bogus input, since there is no check on the reasonableness of the zone abbreviations. For example, SET TIMEZONE TO FOOBAR0 will work, leaving the system effectively using a rather peculiar abbreviation for GMT.