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

From Tom Lane
Subject pgsql: Don't reset changes_since_analyze after a selective-columns ANAL
Date
Msg-id E1bA2K5-0006An-Aq@gemulon.postgresql.org
Whole thread Raw
List 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@ato.waw.pl>

Branch
------
master

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

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(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Stop the executor if no more tuples can be sent from worker to l
Next
From: Tom Lane
Date:
Subject: pgsql: Don't reset changes_since_analyze after a selective-columns ANAL