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
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
linkend="view-pg-timezone-abbrevs">pg_timezone_abbrevs, many of these names imply a set of daylight-savings transition
date rules. Therefore, the associated information changes across local DST
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.)