Patron user name search crashes

Bug #1643932 reported by Terran McCanna
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
High
Unassigned
2.11
Fix Released
High
Unassigned

Bug Description

In the 2.11 client, searching for a patron by user name (OPAC Login) times out and throws warnings. (It is slow but doesn't time out against the tiny Concerto database, but times out against our full database.)

I'm attaching screenshots of error message & javascript console from the xul client to this ticket.

The web client sometimes times out without an error (just a "No Items to Display" message even though there should be matches), and will sometimes succeed (but is very slow).

Searching by user name in 2.9 against our full database works fine. I don't know if the problem began in 2.10 or 2.11.

Revision history for this message
Terran McCanna (tmccanna) wrote :
Revision history for this message
Terran McCanna (tmccanna) wrote :
Revision history for this message
Chris Sharp (chrissharp123) wrote :

Attaching SQL and EXPLAIN ANALYZE output from a long-running search.

Revision history for this message
Chris Sharp (chrissharp123) wrote :
Changed in evergreen:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Chris Sharp (chrissharp123) wrote :

I can confirm the issue. Setting priority to High since this is pretty close to a showstopper for us.

Revision history for this message
Jason Stephenson (jstephenson) wrote :

You added the unaccent extension to the database?

Revision history for this message
Mike Rylander (mrylander) wrote :

It looks like the upgrade script does not add an index to the usrname field like it does for the various person-name fields. Perhaps we need a:

CREATE INDEX CONCURRENTLY actor_usr_usrname_unaccent_idx ON actor.usr (evergreen.unaccent_and_squash(usrname));

Revision history for this message
Chris Sharp (chrissharp123) wrote :
tags: added: pullrequest
Changed in evergreen:
milestone: none → 2.11.2
Revision history for this message
Terran McCanna (tmccanna) wrote :

Excellent! Thanks, guys!

Revision history for this message
Jason Stephenson (jstephenson) wrote :

I don't think this made it into 2.10, so targeting at 2.11 and 2.next.

Changed in evergreen:
milestone: 2.11.2 → 2.next
Kathy Lussier (klussier)
Changed in evergreen:
milestone: 2.next → 2.12-beta
Revision history for this message
Galen Charlton (gmc) wrote :

Pushed to master and rel_2_11. Thanks, Chris and Mike!

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.