summaryrefslogtreecommitdiff
path: root/src/include
diff options
context:
space:
mode:
authorTom Lane2016-06-06 21:44:18 +0000
committerTom Lane2016-06-06 21:44:18 +0000
commit3201709de3a552113573f73d308b40bba8f73186 (patch)
tree095a5848ad93e051bd78ae47bf5d8a767254a5a9 /src/include
parent294509ea9bb3305230659fd76bd355aec6fcd039 (diff)
Don't reset changes_since_analyze after a selective-columns ANALYZE.
If we ANALYZE only selected columns of a table, we should not postpone auto-analyze because of that; other columns may well still need stats updates. As committed, the counter is left alone if a column list is given, whether or not it includes all analyzable columns of the table. Per complaint from Tomasz Ostrowski. It's been like this a long time, so back-patch to all supported branches. Report: <ef99c1bd-ff60-5f32-2733-c7b504eb960c@ato.waw.pl>
Diffstat (limited to 'src/include')
-rw-r--r--src/include/pgstat.h4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/include/pgstat.h b/src/include/pgstat.h
index a9edf8f6631..f6e7d9fb9ec 100644
--- a/src/include/pgstat.h
+++ b/src/include/pgstat.h
@@ -344,6 +344,7 @@ typedef struct PgStat_MsgAnalyze
Oid m_databaseid;
Oid m_tableoid;
bool m_autovacuum;
+ bool m_resetcounter;
TimestampTz m_analyzetime;
PgStat_Counter m_live_tuples;
PgStat_Counter m_dead_tuples;
@@ -771,7 +772,8 @@ extern void pgstat_report_autovac(Oid dboid);
extern void pgstat_report_vacuum(Oid tableoid, bool shared,
PgStat_Counter tuples);
extern void pgstat_report_analyze(Relation rel,
- PgStat_Counter livetuples, PgStat_Counter deadtuples);
+ PgStat_Counter livetuples, PgStat_Counter deadtuples,
+ bool resetcounter);
extern void pgstat_report_recovery_conflict(int reason);
extern void pgstat_report_deadlock(void);