pgsql: Don't reset changes_since_analyze after a selective-columns ANAL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't reset changes_since_analyze after a selective-columns ANAL
Date: 2016-06-06 21:44:37
Message-ID: E1bA2K5-0006Ar-Ac@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(at)ato(dot)waw(dot)pl>

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/a4400c251f93df7d4f5760ad633c041fc5dae376

Modified Files
--------------
src/backend/commands/analyze.c | 7 +++++--
src/backend/postmaster/pgstat.c | 15 +++++++++++----
src/include/pgstat.h | 4 +++-
3 files changed, 19 insertions(+), 7 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2016-06-07 13:39:52 pgsql: PL/Python: Move ereport wrapper test cases to separate file
Previous Message Robert Haas 2016-06-06 19:16:37 pgsql: Stop the executor if no more tuples can be sent from worker to l