database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-03 22:24:49 +03:00
Code

doc: remove mention of UT1 in representing time

Browse Source 
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
This commit is contained in:
Bruce Momjian 2016-06-28 13:49:37 -04:00
parent c12f02ffc9
commit 675684fc23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/catalogs.sgml
View 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

2
doc/src/sgml/func.sgml
View 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>