zombodb
pg_search
Our great sponsors
zombodb | pg_search | |
---|---|---|
23 | 7 | |
4,608 | 1,229 | |
- | 1.9% | |
8.3 | 6.8 | |
7 days ago | 4 months ago | |
PLpgSQL | Ruby | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zombodb
-
Introducing pgzx: create PostgreSQL extensions using Zig
And lots of interesting extensions use it, like
https://github.com/tembo-io/pgmq
-
Create a search engine with PostgreSQL: Postgres vs Elasticsearch
Point 2 is generally solvable via engineering effort and careful dedicated code. From the existing tools, PGSync is an open source project that aims to specifically solve this problem. ZomboDB is an interesting Postgres extension that tackles point 2 (and I think partially point 3), by controlling and querying Elasticsearch through Postgres. I haven't yet tried either of these two projects, so I can't comment on their trade-offs, but I wanted to mention them.
-
Creating an advanced search engine with PostgreSQL
Curious, did you try zombodb? [https://www.zombodb.com/]
-
💃🏼 Quickwit 0.6 released!🕺🏼: Elasticsearch API compatibility, Grafana plugin, and more....
What about zombodb, do you think that quickwit has all the necessary APIs?
-
Write Postgres functions in Rust
No. Haha. Was just the right name for https://github.com/zombodb/zombodb at the time. Software where the only limit is yourself!
- Integrate PostgreSQL and Elasticsearch – ZomboDB
- Postgres Full Text Search vs. the Rest
- ZomboDB: Making Postgres and Elasticsearch work together like it's 2022
-
Postgres Full-Text Search: A Search Engine in a Database
> The hardest part of building any search engine is keeping the index up-to-date with changes made to the underlying data store.
This deserves mention, as it solves that problem: https://github.com/zombodb/zombodb
From the README:
> ZomboDB brings powerful text-search and analytics features to Postgres by using Elasticsearch as an index type. Its comprehensive query language and SQL functions enable new and creative ways to query your relational data.
> From a technical perspective, ZomboDB is a 100% native Postgres extension that implements Postgres' Index Access Method API. As a native Postgres index type, ZomboDB allows you to CREATE INDEX ... USING zombodb on your existing Postgres tables. At that point, ZomboDB takes over and fully manages the remote Elasticsearch index and guarantees transactionally-correct text-search query results.
I find other things also hard in search engines: dealing with the plethora of human languages and all the requirements we may have to processing them. A mature solution like ES therefor is almost a must in the more demanding cases.
-
State of the art for serde-compatible CBOR encoding/decoding?
You can read more about it on our GitHub repo, but basically it brings most of the power of elasticsearch’s searching and analytics abilities straight into Postgres.
pg_search
-
The Ultimate Search for Rails - Episode 1
On the backend, we'll need a few tools. Apart from the classics (ActiveRecord scopes and the pg_search gem), you’ll see how the (yet officially unreleased but production-tested) all_futures gem, built by SR authors, will act as an ideal ephemeral object to temporarily store our filter params and host our search logic. Finally, we’ll use pagy for pagination duties.
-
Application Search Feature more that ActiveRecord;
You can take a look at pg_search if you’re using Postgres
-
How to build a search engine with Ruby on Rails
This was a really good read, thanks. I've got into the habit of jumping straight to PgSearch but could definitely apply this approach to some existing projects.
-
Instant search with Rails 6 and Hotwire
Cleaner, more performant database queries: Definitely don't just leave your query sitting in the controller! For production use cases, you'd want to consider an option like pg_search
-
Postgres Full-Text Search: A Search Engine in a Database
If you are using Rails with Postgres you can use pg_search gem to build the named scopes to take advantage of full text search.
-
Tips for optimizing pg_search?
Hey guys. Looking to release an app for mobile that will be using a rails API. The app will heavily rely on search. I know the go-to is to use elasticsearch but wanted to see if there was enough user demand for the MVP before shelling out $50/mo for the heroku add on. In the mean time I've been using pg_search. From the eye test it's performing okay but will be adding a table that houses over 350K records. With this in mind I was wondering if you all had any tips for increasing the overall speed for search from the model and controller level. Also should note that I'm open to any other free search gems if they deem bette fit.
-
Rails Search Bar
There are two basic search configurations with pg_search, a Single Model search scope or a multi Model configuration. In my case I am only using the Single Model configuration, but you can read more about multi-search in the documentation.
What are some alternatives?
Typesense - Open Source alternative to Algolia + Pinecone and an Easier-to-Use alternative to ElasticSearch ⚡ 🔍 ✨ Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences
ransack - Object-based searching.
noria - Fast web applications through dynamic, partially-stateful dataflow
Elasticsearch Rails - Elasticsearch integrations for ActiveModel/Record and Ruby on Rails
squawk - 🐘 linter for PostgreSQL, focused on migrations
textacular - Textacular exposes full text search capabilities from PostgreSQL, and allows you to declare full text indexes. Textacular will extend ActiveRecord with named_scope methods making searching easy and fun!
stolon - PostgreSQL cloud native High Availability and more.
elasticsearch-ruby - Ruby integrations for Elasticsearch
helium-etl-queries - A collection of SQL views used to enrich data produced by a Helium blockchain-etl
Searchkick - Intelligent search made easy
pg_cjk_parser - Postgres CJK Parser pg_cjk_parser is a fts (full text search) parser derived from the default parser in PostgreSQL 11. When a postgres database uses utf-8 encoding, this parser supports all the features of the default parser while splitting CJK (Chinese, Japanese, Korean) characters into 2-gram tokens. If the database's encoding is not utf-8, the parser behaves just like the default parser.
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow