From: Bruce Momjian Date: Tue, 28 Jun 2016 17:49:37 +0000 (-0400) Subject: doc: remove mention of UT1 in representing time X-Git-Tag: REL9_6_BETA3~95 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=675684fc23fd4287966694b1f108846bc14b6895;p=postgresql doc: remove mention of UT1 in representing time UT1 was incorrectly specified as our time representation. (UT1 is astronomical time.) We are not actually UTC either because we ignore leap seconds. Reported-by: Thomas Munro Discussion: CAEepm=3-TW9PLwGZhqjSSiEQ9UzJEKE-HELQDzRE0QUSCp8dgw@mail.gmail.com --- diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 18e5faef57..0689cc9720 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -9804,8 +9804,8 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx of time zone names that are recognized by SET TIMEZONE, along with their associated abbreviations, UTC offsets, and daylight-savings status. (Technically, - PostgreSQL uses UT1 rather - than UTC because leap seconds are not handled.) + PostgreSQL does not use UTC because leap + seconds are not handled.) Unlike the abbreviations shown in pg_timezone_abbrevs, many of these names imply a set of daylight-savings transition date rules. Therefore, the associated information changes across local DST diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 98b3995f22..052b8f5ba0 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -7578,7 +7578,7 @@ SELECT EXTRACT(SECOND FROM TIME '17:12:28.5'); The time zone offset from UTC, measured in seconds. Positive values correspond to time zones east of UTC, negative values to zones west of UTC. (Technically, - PostgreSQL uses UT1 because + PostgreSQL does not use UTC because leap seconds are not handled.)