Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables
Date
Msg-id 23152.1413737430@sss.pgh.pa.us
Whole thread Raw
In response to Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> There's rub here though. We unconditionally do:
>     /* Do post-vacuum cleanup and statistics update for each index */
>     for (i = 0; i < nindexes; i++)
>         lazy_cleanup_index(Irel[i], indstats[i], vacrelstats);

> and that's not particularly cheap. Maybe we should make that conditional
> when there's been no lazy_vacuum_index/heap calls at all?

Absolutely not.  If the cleanup step is skippable, it would be the
province of the index AM to make that decision.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables
Next
From: Andres Freund
Date:
Subject: Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables