Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 97f7969

Browse files
committed
Add an explicit comment about POSIX time zone names having the reverse
sign convention from everyplace else in Postgres. I don't suppose that this will stop people from being confused, but at least we can say that it's documented.
1 parent 3b4f9fe commit 97f7969

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

doc/src/sgml/datatype.sgml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.199 2007/05/03 15:05:56 neilc Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.200 2007/05/08 17:02:59 tgl Exp $ -->
22

33
<chapter id="datatype">
44
<title id="datatype-title">Data Types</title>
@@ -2275,6 +2275,11 @@ January 8 04:05:06 1999 PST
22752275
reasonableness of the zone abbreviations. For example, <literal>SET
22762276
TIMEZONE TO FOOBAR0</> will work, leaving the system effectively using
22772277
a rather peculiar abbreviation for UTC.
2278+
Another issue to keep in mind is that in POSIX time zone names,
2279+
positive offsets are used for locations <emphasis>west</> of Greenwich.
2280+
Everywhere else, <productname>PostgreSQL</productname> follows the
2281+
ISO-8601 convention that positive timezone offsets are <emphasis>east</>
2282+
of Greenwich.
22782283
</para>
22792284

22802285
<para>

0 commit comments

Comments
 (0)