]> granicus.if.org Git - postgresql/commitdiff
doc: remove mention of UT1 in representing time
authorBruce Momjian <bruce@momjian.us>
Tue, 28 Jun 2016 17:49:37 +0000 (13:49 -0400)
committerBruce Momjian <bruce@momjian.us>
Tue, 28 Jun 2016 17:49:37 +0000 (13:49 -0400)
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

doc/src/sgml/catalogs.sgml
doc/src/sgml/func.sgml

index 18e5faef5748c763ec022c9d7c128b7717f8fcb3..0689cc97205040a3a3051b390c6346295037b831 100644 (file)
@@ -9804,8 +9804,8 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
    of time zone names that are recognized by <command>SET TIMEZONE</>,
    along with their associated abbreviations, UTC offsets,
    and daylight-savings status.  (Technically,
-   <productname>PostgreSQL</productname> uses <acronym>UT1</> rather
-   than UTC because leap seconds are not handled.)
+   <productname>PostgreSQL</productname> does not use UTC because leap
+   seconds are not handled.)
    Unlike the abbreviations shown in <link
    linkend="view-pg-timezone-abbrevs"><structname>pg_timezone_abbrevs</structname></link>, many of these names imply a set of daylight-savings transition
    date rules.  Therefore, the associated information changes across local DST
index 98b3995f2252d1f3436a3fc76f8d239a079b8aee..052b8f5ba05760d2651d6ad2ee698c49d8fd20c8 100644 (file)
@@ -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,
-        <productname>PostgreSQL</productname> uses <acronym>UT1</> because
+        <productname>PostgreSQL</productname> does not use UTC because
         leap seconds are not handled.)
        </para>
       </listitem>