Pavel Borisov <pashkin.e...@gmail.com> writes: > Now when checking for shortening of leaf tuple is added LongValuesOK > become slightly redundant. I'd propose to replace it with more legible name > as LongValuesOK doesn't mean they are warranted to be ok just that we can > try to shorten them? What about tryShortening, trySuffixing or > can(Try)ShortenTuple?
That field name is part of the opclass API. I fear it's several years
too late to rename it for no compelling reason.
regards, tom lane
