Alvaro Herrera wrote:
I wonder if we could instead make vacuum write a new FSM tree from scratch, rather than updating it piecemeal.
I'd like to move away from that, as we'll hopefully get some sort of partial vacuum capability soon.
We might want to have some sort of bulk update operation, though, so that you could refresh FSM information for say 100 pages, or one FSM page, at a time. That would reduce the WAL traffic of a VACUUM significantly, though I'm not sure how significant that is to begin with.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches
