https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42508
--- Comment #25 from David Cook <[email protected]> --- I just don't understand what the exact pain point is with the current search. 1.5 million rows in a database isn't much. I just searched an unindexed field on a PostgreSQL table with 24.5 million rows and it took 1-2 seconds. PostgreSQL is a superior database system, but still. In a non-Koha app, I have a PostgreSQL table with over 600,000,000 rows. That can be tricky but there's ways of working with that in terms of indexes as well. I know that there has been an issue with search - possibly patron search - in the past where we were searching an unindexed field and I think that one was solved by adding an index. Rather than switching from the database to Elastic, why don't we try to look at the actual problems/root causes? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
