The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Pg_partman Alternatives
Similar projects and alternatives to pg_partman
-
TimescaleDB
An open-source time-series SQL database optimized for fast ingest and complex queries. Packaged as a PostgreSQL extension.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
blog
OpenSource,Database,Business,Minds. git clone --depth 1 https://github.com/digoal/blog (by digoal)
-
postgres-aws-s3
aws_s3 postgres extension to import/export data from/to s3 (compatible with aws_s3 extension on AWS RDS)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
practical-sql
Code and Data for the First Edition of "Practical SQL" by Anthony DeBarros, published by No Starch Press (2018).
pg_partman reviews and mentions
-
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.
-
A note from our sponsor - WorkOS
workos.com | 24 Apr 2024
Stats
pgpartman/pg_partman is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of pg_partman is PLpgSQL.
Sponsored