Re: Allowed timezone values

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Allowed timezone values
Дата
Msg-id 23824.1129225108@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Allowed timezone values  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: Allowed timezone values  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Список pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I am playing with our allowed timezone settings and saw a few strange
> things.  It understands "EST5EDT", but how does it understand "XYT5ABT"?

Because the code in src/timezone does what the POSIX standard says it
must do.  The relevant man page on my HPUX box says
    TZ          TZ sets time zone information.  TZ can be set using the                format:
                        [:]STDoffset[DST[offset][,rule]]
                   where:
                      STD and DST Three or more bytes that designate the                                  standard time
zone(STD) and summer (or                                  daylight-savings) time zone (DST) STD is
           required.  If DST is not specified,                                  summer time does not apply in this
                           locale.  Any characters other than                                  digits, comma (,), minus
(-),plus (+),                                  or ASCII NUL are allowed.
 
                      offset      offset is the value that must be added                                  to local time
toarrive at Coordinated                                  Universal Time (UTC).  Offset is of the
         form :
 
                                       hh[:mm[:ss]]
        ... etc etc ...

> Also, JST doesn't work anymore, but JST9 does.

JST9 is valid per the POSIX rules.  JST isn't listed as a zone name in
the zic database, so it's not valid.  (Try "Japan" instead.)
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: A costing analysis tool
Следующее
От: Mark Wong
Дата:
Сообщение: Re: Spinlocks, yet again: analysis and proposed patches