From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Collin Peters" <cadiolis(at)gmail(dot)com> |
Cc: | "Adrian Klaver" <aklaver(at)comcast(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Timezone issue - Is it me or is this a massive bug? |
Date: | 2008-06-23 18:08:43 |
Message-ID: | 28581.1214244523@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Collin Peters" <cadiolis(at)gmail(dot)com> writes:
> I have read the post and understand the issue. I am wondering why
> this is not mentioned in the documentation.
It is. Per
http://www.postgresql.org/docs/8.3/static/datatype-datetime.html#DATATYPE-TIMEZONES
"One should be wary that the POSIX-style time zone feature 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 UTC. Another issue to keep in mind is that in
POSIX time zone names, positive offsets are used for locations west of
Greenwich. Everywhere else, PostgreSQL follows the ISO-8601 convention
that positive timezone offsets are east of Greenwich."
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2008-06-23 18:21:12 | Re: limits? |
Previous Message | Mike Gould | 2008-06-23 18:00:46 | Data Types |