Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit7417a8e

Browse files
committed
Improve a couple of 9.2 release note entries.
Clarify the compatibility notes about EXTRACT() and about statisticstiming columns.
1 parent8770328 commit7417a8e

File tree

1 file changed

+22
-15
lines changed

1 file changed

+22
-15
lines changed

‎doc/src/sgml/release-9.2.sgml

Lines changed: 22 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,8 @@
196196
</para>
197197

198198
<para>
199-
Without this it is possible to output invalid <acronym>XML</acronym>.
199+
Without this it is possible for the result not to be valid
200+
<acronym>XML</acronym>.
200201
</para>
201202
</listitem>
202203

@@ -216,15 +217,20 @@
216217
<listitem>
217218
<para>
218219
Make <link
219-
linkend="functions-datetime-extract"><function>EXTRACT</></link> of
220-
a non-timezone-aware value measure the epoch from local midnight,
221-
not <acronym>UTC</acronym> midnight (Tom Lane)
220+
linkend="functions-datetime-extract"><function>EXTRACT(EPOCH FROM
221+
<replaceable>timestamp without time zone</>)</function></link>
222+
measure the epoch from local midnight, not <acronym>UTC</acronym>
223+
midnight (Tom Lane)
222224
</para>
223225

224226
<para>
225-
Having these computations depend on <acronym>UTC</acronym>
226-
was inconsistent. The old behavior is available by casting the
227-
value to timestamp with time zone.
227+
This change reverts an ill-considered change made in release 7.3.
228+
Measuring from <acronym>UTC</acronym> midnight was inconsistent
229+
because it made the result dependent on the <link
230+
linkend="guc-timezone"><varname>timezone</></link> setting, which
231+
computations for <type>timestamp without time zone</> should not be.
232+
The previous behavior remains available by casting the input value
233+
to <type>timestamp with time zone</>.
228234
</para>
229235
</listitem>
230236

@@ -462,20 +468,21 @@
462468
</para>
463469

464470
<para>
471+
This change eliminates the designed-in assumption that the values
472+
are accurate to microseconds and no more (since the <type>float8</>
473+
values can be fractional).
465474
The columns affected are
466475
<structname>pg_stat_user_functions</>.<structfield>total_time</>,
467476
<structname>pg_stat_user_functions</>.<structfield>self_time</>,
468477
<structname>pg_stat_xact_user_functions</>.<structfield>total_time</>,
469478
and
470479
<structname>pg_stat_xact_user_functions</>.<structfield>self_time</>.
471-
</para>
472-
</listitem>
473-
474-
<listitem>
475-
<para>
476-
Change <application>pg_stat_statements</>'
477-
<structfield>total_time</> column to be measured in milliseconds
478-
(Tom Lane)
480+
The statistics functions underlying these columns now also return
481+
<type>float8</> milliseconds, rather than <type>bigint</>
482+
microseconds.
483+
<filename>contrib/pg_stat_statements</>'
484+
<structfield>total_time</> column is now also measured in
485+
milliseconds.
479486
</para>
480487
</listitem>
481488

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp