2014-03-28 9:22 GMT+01:00 Peter Geoghegan <p...@heroku.com>: > 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. >
if it is related to ERRCODE_UNDEFINED_COLUMN then it should be ok (from performance perspective) but second issue can be usage from plpgsql - where is mix SQL identifiers and plpgsql variables. Pavel > > > -- > Peter Geoghegan >
