aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-03-02 11:22:42 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-03-02 11:22:42 -0500
commit81b9b5ce490a645bde8df203ec4a3b2903d88f31 (patch)
treec9926c22a7029baa1915cc3846f3f2a128683f77 /contrib/postgres_fdw/postgres_fdw.c
parent7240962f8626ff09bb8f9e71ecdb074775bdd035 (diff)
downloadpostgresql-81b9b5ce490a645bde8df203ec4a3b2903d88f31.tar.gz
postgresql-81b9b5ce490a645bde8df203ec4a3b2903d88f31.zip
Make gistvacuumcleanup() count the actual number of index tuples.
Previously, it just returned the heap tuple count, which might be only an estimate, and would be completely the wrong thing if the index is partial. Since this function scans every index page anyway to find free pages, it's practically free to count the surviving index tuples. Let's do that and return an accurate count. This is easily visible as a wrong reltuples value for a partial GiST index following VACUUM, so back-patch to all supported branches. Andrey Borodin, reviewed by Michail Nikolaev Discussion: https://postgr.es/m/151956654251.6915.675951950408204404.pgcf@coridan.postgresql.org
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions