Comment 19 for bug 1549505

And to expand on Mike's explanation: the issue occurs when a given Pg backend processes a normal bib search, thereby caching a compiled version of query_parser_fts with one shape of the core result query output, then subsequently processes (say) a has_browse_entry() search.