EDI: fetcher's check of duplicate files can be too slow

[Galen Charlton]

When acq.edi_message is very large (either because of the passage of time or as a consequence of bug 1662902), the query that edi_fetcher.pl runs to see if a remote file had been previously proceeded can take a long time. In particular, we've observed a case where it could take over two minutes, thereby running into a timeout and causing edi_fetcher.pl to crash.

The query in question currently uses "ilike", for which PostgreSQL does not well support use of indexes; I propose to replace that with use of evergreen.lowercase().

Evergreen master

[Galen Charlton (gmc)]

A patch is available in the user/gmcharlt/lp1673799_speed_up_dupe_edi_file_check branch in the working/Evergreen repository:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp1673799_speed_up_dupe_edi_file_check

[Bill Erickson (berick)]

Confirmed modified query and index resulted in queries taking milliseconds instead of seconds. Also confirmed new query is looking for the same data. Merged to 2.11 and higher. Thanks, Galen!