pg_partman
zombodb
pg_partman | zombodb | |
---|---|---|
7 | 23 | |
1,879 | 4,608 | |
2.4% | - | |
7.0 | 8.3 | |
23 days ago | 23 days ago | |
PLpgSQL | PLpgSQL | |
GNU General Public License v3.0 or later | 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.
pg_partman
-
Dear data engineers
Assuming these are the types of insights you're looking for, you'll probably look for a way to aggregate data points across/within geographies. postgis is an open source extension for postgres that can help you with this, but there's also quite a few python tools that can help you explore the data, such as geopandas, folium, geoplot. Depending on volume, you might want to partition the data for query performance, and there's another extension pg_partman that can help with that. Just noticed some other posts have recommended something similar.
- Pgpartman: Partition Management Extension for Postgres
-
Which is the best way to automate backing up data monthly of tables in a schema and then deleting them?
pg_partman is in RDS >12.5 (here). Pg_partman makes managing data retention relatively easy.
- Partitioning in Postgres, 2022 Edition
-
TimescaleDB 2.7 vs. PostgreSQL 14
Whenever I see these posts from TimescaleDB, I always want to ask them how it compares in performance to alternative extensions that implement the same features, rather than just comparing TimescaleDB to vanilla PostgreSQL.
For example, they mention their automated data retention and how it's achieved with one SQL command, and how DELETEing records is a very costly operation, and how "even if you were using Postgres declarative partitioning you’d still need to automate the process yourself, wasting precious developer time, adding additional requirements, and implementing bespoke code that needs to be supported moving forward".
There's zero mention anywhere of pg_partman, which does all of these things for you equally as simply, and is a fully OSS free alternative [0].
I get that it's a PG extension that competes with their product. I know that TimescaleDB does a few other things that pg_partman does not. But I can't help but find its (seemingly) purposeful omission in these, otherwise very thorough blog posts, misleading.
[0] https://github.com/pgpartman/pg_partman/blob/master/doc/pg_p...
-
Table partitioning by months of the year?
Take a look into this extension which would take care of a good amount of automation for you.
-
Replicating a dynamically partitioned table possible in Postgres 13
You might want to look into pg_partman which has many useful tools around semi-automatic partitioning. According to their documentation they already have a procedure that will do exactly that: create new partitions based on the rows in the default partition.
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?
periods - PERIODs and SYSTEM VERSIONING for PostgreSQL
pg_search - pg_search builds ActiveRecord named scopes that take advantage of PostgreSQL’s full text search
pgddl - DDL eXtractor functions for PostgreSQL (ddlx)
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
blog - OpenSource,Database,Business,Minds. git clone --depth 1 https://github.com/digoal/blog
noria - Fast web applications through dynamic, partially-stateful dataflow
postgres-aws-s3 - aws_s3 postgres extension to import/export data from/to s3 (compatible with aws_s3 extension on AWS RDS)
squawk - 🐘 linter for PostgreSQL, focused on migrations
practical-sql - Code and Data for the First Edition of "Practical SQL" by Anthony DeBarros, published by No Starch Press (2018).
stolon - PostgreSQL cloud native High Availability and more.
metagration - Metagration: PostgreSQL Migrator in PostgreSQL
helium-etl-queries - A collection of SQL views used to enrich data produced by a Helium blockchain-etl