On Sat, Dec 20, 2014 at 3:17 PM, Peter Geoghegan <p...@heroku.com> wrote: > Attached patch implements this scheme.
I had another thought: "NAMEDATALEN + 1" is a better representation of "infinity" for matching purposes than INT_MAX. I probably should have made that change, too. It would then not have been necessary to "#include <limits.h>". I think that this is a useful belt-and-suspenders precaution against integer overflow. It almost certainly won't matter, since it's very unlikely that the best match within an RTE will end up being a dropped column, but we might as well do it that way (Levenshtein distance is costed in multiples of code point changes, but the maximum density is 1 byte per codepoint). -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
