On Fri, Mar 28, 2014 at 5:57 AM, Michael Paquier <michael.paqu...@gmail.com> wrote: > What about the overhead that this processing creates if error > processing needs to scan a schema with let's say hundreds of tables?
It doesn't work that way. I've extended searchRangeTableForCol() so that when it calls scanRTEForColumn(), it considers Levenshtein distance, and not just plain string equality, which is what happens today. The code only looks through ParseState. -- 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
