Re: New vacuum option to do only freezing
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Sawada Masahiko <sawada.mshk@gmail.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2018-11-08T17:56:00Z
Lists: pgsql-hackers
On Thu, Nov 8, 2018 at 4:36 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > We already have disable_page_skipping option, not (page_skipping > false). So ISMT disable_index_cleanup would be more natural. Sure. > Also, > since what to do with this option is not only skipping vacuum indexes > but also skipping removeing dead tuples on heap, I think that the > option should have a more understandable name for users indicating > that both it removes dead tuples less than the normal vacuum and it's > aimed to freeze tuple more faster. Of course we document them, though. Well, I actually don't think that you should control two behaviors with the same option. If you want to vacuum and skip index cleanup, you should say VACUUM (disable_index_cleanup). If you want to vacuum, disable index cleanup, and skip aggressively, you should say VACUUM (freeze, disable_index_cleanup). Both behaviors seem useful. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Add toast-level reloption for vacuum_index_cleanup
- ce59b75d449d 12.0 landed
-
heap_prepare_freeze_tuple: Simplify coding
- 2bf372a4ae26 12.0 landed
-
Fix missing word.
- 6665305e17ed 12.0 landed
-
Allow VACUUM to be run with index cleanup disabled.
- a96c41feec6b 12.0 landed
-
Don't mark pages all-visible spuriously
- d2599ecfcc74 11.0 cited