On 2016-07-08 11:00:50 -0500, Kevin Grittner wrote: > On Wed, Jul 6, 2016 at 4:55 PM, Andres Freund <and...@anarazel.de> wrote: > > > So I don't think that approach still allows old snapshot related > > cleanups for toast triggered vacuums? Is that an acceptable > > restriction? > > What I would rather see is that if the heap is vacuumed (whether or > not by autovacuum) then the related TOAST table is also vacuumed > (using the same horizon the heap used), but if the TOAST relation > is chosen for vacuum by itself that it does not attempt to adjust > the horizon based on old_snapshot_threshold.
Uh, wouldn't that quote massively regress the autovacuum workload in some cases? There's a reason they're considered separately after all. And in many cases, even if there's lots of updates in the heap table, the toast table doesn't get any updates. And the toast table is often a lot larger than the data. Regards, Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
