Tom Lane wrote:
>
> ISTM the point of the delay parameters
> for autovac is to put a lid on its impact on interactive response. Seen
> in that light, you do not care exactly which table it's hitting at the
> moment.
Unless the table in question takes a big lock when it's VACUUMed
like tables with GiST indexes do today.
Slowing down one of those vacuums on a larger table has a huge
impact on interactive responses.
With GiST indexes becoming concurrent I assume Vacuum won't lock
anymore on my tables; but I don't know if there are other index
types or condition that might make vacuums take out similar
table-wide locks.
Ron
