Wouldn't a table-level option like 'apply_index_scan' be better than a
subscription-level option with a default value as false? Anyway, the
bigger point is that we don't see a better way to proceed here than to
introduce some option to control this behavior.
What would be a good API for adding such an option for table-level?
To be more specific, I cannot see any table level sub/pub options in the docs.
My main motivation for doing it for subscription-level is that (a) it might be
too much work for users to control the behavior if it is table-level (b) I couldn't
find a good API for table-level, and inventing a new one seemed
like a big change.
Overall, I think it makes sense to disable the feature by default. It is
enabled by default, and that's good for test coverage for now, but
let me disable it when I push a version next time.
I see this as a way to provide this feature for users but I would
prefer to proceed with this if we can get some more buy-in from senior
community members (at least one more committer) and some user(s) if
possible. So, I once again request others to chime in and share their
opinion.
Agreed, it would be great to hear some other perspectives on this.
Thanks,
Onder