diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-11-01 13:57:31 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-11-01 13:57:31 -0400 |
| commit | 45f64f1bbf19283795762df6a54f9aa74fee05f7 (patch) | |
| tree | 147fc9b2af824f6503f77b0ea2e14d2e7fdd6172 /doc/src | |
| parent | 1c8a7f617fd1d38cb0540266e4fca6835f61005a (diff) | |
| download | postgresql-45f64f1bbf19283795762df6a54f9aa74fee05f7.tar.gz postgresql-45f64f1bbf19283795762df6a54f9aa74fee05f7.zip | |
Remove CTimeZone/HasCTZSet, root and branch.
These variables no longer have any useful purpose, since there's no reason
to special-case brute force timezones now that we have a valid
session_timezone setting for them. Remove the variables, and remove the
SET/SHOW TIME ZONE code that deals with them.
The user-visible impact of this is that SHOW TIME ZONE will now show a
POSIX-style zone specification, in the form "<+-offset>-+offset", rather
than an interval value when a brute-force zone has been set. While perhaps
less intuitive, this is a better definition than before because it's
actually possible to give that string back to SET TIME ZONE and get the
same behavior, unlike what used to happen.
We did not previously mention the angle-bracket syntax when describing
POSIX timezone specifications; add some documentation so that people
can figure out what these strings do. (There's still quite a lot of
undocumented functionality there, but anybody who really cares can
go read the POSIX spec to find out about it. In practice most people
seem to prefer Olsen-style city names anyway.)
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/datatype.sgml | 7 | ||||
| -rw-r--r-- | doc/src/sgml/ref/set.sgml | 9 |
2 files changed, 14 insertions, 2 deletions
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 07f0385d80d..dea5195786a 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -2419,8 +2419,11 @@ January 8 04:05:06 1999 PST optional daylight-savings zone abbreviation, assumed to stand for one hour ahead of the given offset. For example, if <literal>EST5EDT</> were not already a recognized zone name, it would be accepted and would - be functionally equivalent to United States East Coast time. When a - daylight-savings zone name is present, it is assumed to be used + be functionally equivalent to United States East Coast time. In this + syntax, a zone abbreviation can be a string of letters, or an + arbitrary string surrounded by angle brackets (<literal><></>). + When a daylight-savings zone abbreviation is present, + it is assumed to be used according to the same daylight-savings transition rules used in the <literal>zoneinfo</> time zone database's <filename>posixrules</> entry. In a standard <productname>PostgreSQL</productname> installation, diff --git a/doc/src/sgml/ref/set.sgml b/doc/src/sgml/ref/set.sgml index d108dd4831c..6290c9de708 100644 --- a/doc/src/sgml/ref/set.sgml +++ b/doc/src/sgml/ref/set.sgml @@ -243,7 +243,16 @@ SELECT setseed(<replaceable>value</replaceable>); </listitem> </varlistentry> </variablelist> + </para> + <para> + Timezone settings given as numbers or intervals are internally + translated to POSIX timezone syntax. For example, after + <literal>SET TIME ZONE -7</>, <command>SHOW TIME ZONE</> would + report <literal><-07>+07</>. + </para> + + <para> See <xref linkend="datatype-timezones"> for more information about time zones. </para> |