On Tue, Apr 23, 2019 at 7:09 AM Masahiko Sawada <sawada.m...@gmail.com> wrote: > For the second issue, I've changed lazy vacuum so that it reports both > the number of kilobytes we freed and the number of kilobytes can be > freed after index cleanup.
I am not very convinced that this reporting is in any useful to users. Despite N kilobytes of tuples having been freed, the pages themselves are still allocated and the actual ability to reuse that space may be dependent on lots of factors that the user can't control like the sizes of newly-inserted tuples and the degree to which the free space map is accurate. I feel like we're drifting off into inventing new kinds of reporting here instead of focusing on fixing the reported defects of the already-committed patch, but perhaps I am taking too narrow a view of the situation. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
