On 3/3/19, 9:23 PM, "Masahiko Sawada" <sawada.m...@gmail.com> wrote: > FWIW, I agree that we have options for vacuum as vacuum > command options. But for reloptions, I think if the persistence the > setting could be problematic we should not. According to the > discussions so far, I think VACUUM_SHRINK_ENABLED is the one option > that can be available as both vacuum command option and reloptions. > But I'm not sure there is good use case even if we can set > DISABLE_INDEX_CLEANUP as reloptions.
+1 The DISABLE_INDEX_CLEANUP option is intended to help avoid transaction ID wraparound and should not be used as a long-term VACUUM strategy for a table. Nathan
