On Fri, Jan 11, 2019 at 1:14 AM Masahiko Sawada <sawada.m...@gmail.com> wrote:
> Attached the updated patch. Please review it.
I'm quite confused by this patch. It seems to me that the easiest way
to implement this patch would be to (1) make lazy_space_alloc take the
maxtuples = MaxHeapTuplesPerPage branch when the new option is
specified, and then (2) forget about them after each page i.e.
if (nindexes == 0 &&
vacrelstats->num_dead_tuples > 0)
{
...
}
else if (skipping index cleanup)
vacrelstats->num_dead_tuples = 0;
I don't see why it should touch the logic inside lazy_vacuum_page() or
the decision about whether to truncate.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
