WIP patch for system-catalog vacuuming via a relationmap
in [PgSql]
|
Prev: Confusion over Python drivers
Next: Add on_plperl_init and on_plperlu_init to plperl UPDATE 3 [PATCH]
From: Josh Berkus on 5 Feb 2010 17:22 > Barring objections I'm going to press ahead with completing and > committing this; then in a separate patch remove VACUUM FULL INPLACE. Was it our determination that we could remove VFI if we eliminated the system catalogs? I'm fine with it, I just thought some people had a marginal use case for VFI. --Josh Berkus -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Heikki Linnakangas on 5 Feb 2010 19:24
Tom Lane wrote: > Josh Berkus <josh(a)agliodbs.com> writes: >>> Barring objections I'm going to press ahead with completing and >>> committing this; then in a separate patch remove VACUUM FULL INPLACE. > >> Was it our determination that we could remove VFI if we eliminated the >> system catalogs? I'm fine with it, I just thought some people had a >> marginal use case for VFI. > > I thought the consensus was to remove it if possible. There may still > be some "marginal" use cases, but they don't justify the work that'd > be needed to make it play safely with HS; let alone fixing the other > longstanding gotchas with it, like the double-commit risk. I think part of the plan was to also provide an online reorg tool that works by doing dummy UPDATEs, which means that you can get serialization errors in serializable mode, but doesn't need to lock the table. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |