On Thu, Nov 8, 2018 at 4:36 AM Masahiko Sawada <sawada.m...@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
