diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index 7a279f04d0e..4b8406045e7 100644
--- a/doc/src/sgml/release-9.2.sgml
+++ b/doc/src/sgml/release-9.2.sgml
@@ -196,7 +196,8 @@
- Without this it is possible to output invalid XML.
+ Without this it is possible for the result not to be valid
+ XML.
@@ -216,15 +217,20 @@
Make EXTRACT> of
- a non-timezone-aware value measure the epoch from local midnight,
- not UTC midnight (Tom Lane)
+ linkend="functions-datetime-extract">EXTRACT(EPOCH FROM
+ timestamp without time zone>)
+ measure the epoch from local midnight, not UTC
+ midnight (Tom Lane)
- Having these computations depend on UTC
- was inconsistent. The old behavior is available by casting the
- value to timestamp with time zone.
+ This change reverts an ill-considered change made in release 7.3.
+ Measuring from UTC midnight was inconsistent
+ because it made the result dependent on the timezone> setting, which
+ computations for timestamp without time zone> should not be.
+ The previous behavior remains available by casting the input value
+ to timestamp with time zone>.
@@ -462,20 +468,21 @@
+ This change eliminates the designed-in assumption that the values
+ are accurate to microseconds and no more (since the float8>
+ values can be fractional).
The columns affected are
pg_stat_user_functions>.total_time>,
pg_stat_user_functions>.self_time>,
pg_stat_xact_user_functions>.total_time>,
and
pg_stat_xact_user_functions>.self_time>.
-
-
-
-
-
- Change pg_stat_statements>'
- total_time> column to be measured in milliseconds
- (Tom Lane)
+ The statistics functions underlying these columns now also return
+ float8> milliseconds, rather than bigint>
+ microseconds.
+ contrib/pg_stat_statements>'
+ total_time> column is now also measured in
+ milliseconds.