database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-02 11:44:50 +03:00
Code

Improve a couple of 9.2 release note entries.

Browse Source 
Clarify the compatibility notes about EXTRACT() and about statistics
timing columns.
This commit is contained in:
Tom Lane 2012-08-27 20:54:00 -04:00
parent 60888e232f
commit a63b7744fa
1 changed files with 22 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
doc/src/sgml/release-9.2.sgml
View File

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