Thanks to visit codestin.com
Credit goes to postgrespro.com

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 [email protected]
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: <[email protected]>

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/5f3e0e84b274dbbe605cd2d4c2717c14e2cfe787

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: Tom Lane
Date:
Subject: pgsql: Don't reset changes_since_analyze after a selective-columns ANAL
Next
From: Tom Lane
Date:
Subject: pgsql: Don't reset changes_since_analyze after a selective-columns ANAL