Comment 15 for bug 1549505

Kathy,

I was able to reproduce this by applying the fixed function and then immediately attempting a search without restarting services. It looks like it's a postgres bug having to do with cached query plans. Those only last for the length of a database session, so a restart of services (reconnecting to the database) fixes it.

Can you confirm that works for you?

Thanks!