helium-etl-queries
zombodb
| helium-etl-queries | zombodb | |
|---|---|---|
| 1 | 23 | |
| 15 | 4,608 | |
| - | - | |
| 0.0 | 8.3 | |
| over 1 year ago | 22 days ago | |
| PLpgSQL | PLpgSQL | |
| - | GNU General Public License v3.0 or later |
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.
helium-etl-queries
zombodb
-
Introducing pgzx: create PostgreSQL extensions using Zig
And lots of interesting extensions use it, like
https://github.com/tembo-io/pgmq
https://github.com/zombodb/zombodb
https://github.com/supabase/pg_jsonschema
-
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.
What are some alternatives?
blockchain-etl - Blockchain follower that follows and stores the Helium blockchain
pg_search - pg_search builds ActiveRecord named scopes that take advantage of PostgreSQL’s full text search