Postgres Full-Text Search: A search engine in a database (blog.crunchydata.com)

Article summary

The article discusses Postgres full-text search capabilities, including ignoring stop words, stemming, and weighting and ranking search matches. It provides an example of searching storm event details using Postgres' built-in full-text search. The article highlights the benefits of using Postgres' built-in search functionality, including not having to maintain an additional system. However, it also notes that Postgres search may not be suitable for very large datasets or complex search queries.

Main themes

• Postgres full-text search
• search scalability
• ZomboDB
• Elasticsearch
• system maintenance
• search performance
• data consistency

What commenters say

• Postgres full-text search is a viable option for many use cases, but may not be suitable for very large datasets or complex search queries.
• Using Postgres search can simplify system maintenance by eliminating the need for an additional search system.
• ZomboDB is an alternative that allows using Elasticsearch from Postgres seamlessly, but may have its own limitations and trade-offs.
• Scaling Postgres search can be a challenge, and some users have reported issues with performance and reliability at large scales.
• Some users prefer to use separate systems for search and transactional data to avoid performance issues and ensure consistency.
• Postgres search may not support certain advanced search features, such as sophisticated linguistic and feature scoring pipelines.
• The choice between using Postgres search and a dedicated search system like Elasticsearch depends on the specific use case and requirements.