pg_dump: Small message adjustment for consistency
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/dd024c22f1fff083065b42af555a3552721fabfd
Modified Files
--
src/bin/pg_dump/pg_backup_custom.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
Silence compiler warning about uninitialized variable.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/98316e211b60cb160247171e3557b40a247c4610
Modified Files
--
contrib/pg_upgrade/exec.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
Se
New GUC, track_iotiming, to track I/O timings.
Currently, the only way to see the numbers this gathers is via
EXPLAIN (ANALYZE, BUFFERS), but the plan is to add visibility through
the stats collector and pg_stat_statements in subsequent patches.
Ants Aasma, reviewed by Greg Smith, with some furth
Bend parse location rules for the convenience of pg_stat_statements.
Generally, the parse location assigned to a multiple-token construct is
the location of its leftmost token. This commit breaks that rule for
the syntaxes TYPENAME 'LITERAL' and CAST(CONSTANT AS TYPENAME) --- the
resulting Const
Add some infrastructure for contrib/pg_stat_statements.
Add a queryId field to Query and PlannedStmt. This is not used by the
core backend, except for being copied around at appropriate times.
It's meant to allow plug-ins to track a particular query forward from
parse analysis to execution.
The
Expose track_iotiming information via pg_stat_statements.
Ants Aasma, reviewed by Greg Smith, with very minor tweaks by me.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5b4f346611431361339253203d486789e4babb02
Modified Files
--
.../pg_stat_statements-
pg_test_timing utility, to measure clock monotonicity and timing cost.
Ants Aasma, Greg Smith
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/cee523867db29c0bfc5de7ec638ce0a4ad9b3817
Modified Files
--
contrib/Makefile|1 +
cont