diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-04-30 14:02:47 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-04-30 14:03:33 -0400 |
commit | 809e7e21af8cd24855f1802524a13bbaa823f929 (patch) | |
tree | 450387adf177bd65f21de4c29d6428852608a8b4 /src/backend/access/gist/gist.c | |
parent | 26471a51fc833e2ce58a2f16f891256d57dd28c6 (diff) | |
download | postgresql-809e7e21af8cd24855f1802524a13bbaa823f929.tar.gz postgresql-809e7e21af8cd24855f1802524a13bbaa823f929.zip |
Converge all SQL-level statistics timing values to float8 milliseconds.
This patch adjusts the core statistics views to match the decision already
taken for pg_stat_statements, that values representing elapsed time should
be represented as float8 and measured in milliseconds. By using float8,
we are no longer tied to a specific maximum precision of timing data.
(Internally, it's still microseconds, but we could now change that without
needing changes at the SQL level.)
The columns affected are
pg_stat_bgwriter.checkpoint_write_time
pg_stat_bgwriter.checkpoint_sync_time
pg_stat_database.blk_read_time
pg_stat_database.blk_write_time
pg_stat_user_functions.total_time
pg_stat_user_functions.self_time
pg_stat_xact_user_functions.total_time
pg_stat_xact_user_functions.self_time
The first four of these are new in 9.2, so there is no compatibility issue
from changing them. The others require a release note comment that they
are now double precision (and can show a fractional part) rather than
bigint as before; also their underlying statistics functions now match
the column definitions, instead of returning bigint microseconds.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions