PostgreSQL text-search performance
Quick summary
The article discusses a comparison between PostgreSQL and Oracle text-search performance. PostgreSQL’s capabilities made it possible to implement Koo’s text search quickly and provide fast results from OpenERP data.
Contents
We have talked several times about the text-search capabilities of Koo. Recently, however, we came across this article comparing the performance of PostgreSQL text search with Oracle’s.
The comparison shows once again that PostgreSQL can compete with the major players. PostgreSQL’s performance and features allowed us to implement Koo’s text-search functionality quickly, providing users with fast results from the data stored in OpenERP. And at your company, are you already more productive thanks to text search?
Frequently asked questions
Which performance comparison does the article discuss?
It compares PostgreSQL text search with Oracle’s.
What conclusion does the comparison reach?
The comparison shows that PostgreSQL can compete with systems considered major players.
How is PostgreSQL related to Koo’s text search?
Its performance and features made it possible to implement Koo’s text search quickly.
What does this feature allow users to do with OpenERP data?
It provides users with fast results from the data stored in OpenERP.
Related articles
Tryton
KooRunner: Koo’s full-text search integrated with the desktop
KooRunner connects Koo’s `full_text_search` module with KRunner, the KDE desktop tool for launching applications, searching for information and converting units. This brings ERP searches directly to the desktop used by KDE users.
Open Source and Trends
What is PostgreSQL?
This article explains how to customize BABI reports and charts through Dimensions, Column Dimensions, Measures, Order and Groups. It shows how to structure data, choose aggregations, control presentation order and define which user groups can access each report.
Developer
Koo performance improvements
Koo has gained performance through deferred loading of images, relational fields and view settings, along with fewer unnecessary server calls and faster navigation back to list views. On one very large product form, loading time fell from 10 seconds to 2, although the improvement depends on the data. The article invites the community to test the latest changes and report how they behave.