On 18.01.2012 23:38, YAMAMOTO Takashi wrote:
i'm wondering because what gistVacuumUpdate used to do does not seem to be necessarily tied to the old-style VACUUM FULL. currently, no one will re-union keys after tuple removals, right?
Right. I believe gistVacuumUpdate needed an AccessExclusiveLock, so now that VACUUM FULL is gone, there is no good moment to do it.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
