On Fri, Mar 28, 2014 at 1:00 AM, Pavel Stehule <pavel.steh...@gmail.com> wrote: > I see only one risk - it can do some slowdown of exception processing.
I think it's unlikely that you'd see ERRCODE_UNDEFINED_COLUMN in procedural code like that in practice. In any case it's worth noting that I continually pass back a "max" to the Levenshtein distance implementation, which is the current shortest distance observed. The implementation is therefore not obliged to exhaustively find a distance that is already known to be of no use. See commit 604ab0. -- 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
