| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ross Williams" <ross(dot)williams(at)watchguard(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5912: Etc/GMT time utc offset error |
| Date: | 2011-03-03 17:24:21 |
| Message-ID: | 10585.1299173061@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Ross Williams" <ross(dot)williams(at)watchguard(dot)com> writes:
> On the target OS the offsets are correct GMT+ gives a increased utc_offset.
> When I attempt to set via postgres, the timezone are flipped + for - and
> vice versa.
The problem is that there are conflicting standards for the sign of UTC
offsets. The conventions Postgres has chosen are not 100% consistent,
but neither is the real world. There's some discussion in this
section of the manual:
http://www.postgresql.org/docs/8.4/static/datatype-datetime.html#DATATYPE-TIMEZONES
in particular this bit:
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 | Pavel Stehule | 2011-03-03 17:54:40 | Re: BUG #5867: wish: plpgsql print table for debug |
| Previous Message | Tom Lane | 2011-03-03 17:16:53 | Re: can't build contrib/uuid-ossp |