diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-06-06 17:44:17 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-06-06 17:44:17 -0400 |
| commit | 5acc58c5e5336d16a1e238e8f1d599e8bfa4183b (patch) | |
| tree | 4bd2a422d57d670411779dd9acb51683150b991a /src/backend/access/gist/gistscan.c | |
| parent | a7aa61ffe7ed12cf8d5cbdfc887900549f9ed354 (diff) | |
| download | postgresql-5acc58c5e5336d16a1e238e8f1d599e8bfa4183b.tar.gz postgresql-5acc58c5e5336d16a1e238e8f1d599e8bfa4183b.zip | |
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/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions