|
196 | 196 | </para> |
197 | 197 |
|
198 | 198 | <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>. |
200 | 201 | </para> |
201 | 202 | </listitem> |
202 | 203 |
|
|
216 | 217 | <listitem> |
217 | 218 | <para> |
218 | 219 | 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) |
222 | 224 | </para> |
223 | 225 |
|
224 | 226 | <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</>. |
228 | 234 | </para> |
229 | 235 | </listitem> |
230 | 236 |
|
|
462 | 468 | </para> |
463 | 469 |
|
464 | 470 | <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). |
465 | 474 | The columns affected are |
466 | 475 | <structname>pg_stat_user_functions</>.<structfield>total_time</>, |
467 | 476 | <structname>pg_stat_user_functions</>.<structfield>self_time</>, |
468 | 477 | <structname>pg_stat_xact_user_functions</>.<structfield>total_time</>, |
469 | 478 | and |
470 | 479 | <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. |
479 | 486 | </para> |
480 | 487 | </listitem> |
481 | 488 |
|
|