pgkit
pgreplay
| pgkit | pgreplay | |
|---|---|---|
| 7 | 2 | |
| 28 | 205 | |
| - | - | |
| 7.5 | 4.2 | |
| 7 months ago | 7 months ago | |
| Python | C | |
| MIT License | 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.
pgkit
- Versioning data in Postgres? Testing a Git like approach
- A PostgreSQL Docker container that automatically upgrades PostgreSQL
- [🅿🅶🅺🅸🆃] Pgkit - Postgres Backup, PITR and recovery management made easy
-
[🅿🅶🅺🅸🆃] Pgkit - Backup, PITR and recovery management made easy
Check the demo: https://github.com/SadeghHayeri/pgkit
pgreplay
-
Versioning data in Postgres? Testing a Git like approach
pgreplay parses not the WAL Write Ahead Log but the log file: https://github.com/laurenz/pgreplay
From "A PostgreSQL Docker container that automatically upgrades your database" (2023) https://news.ycombinator.com/item?id=36748041 :
pgkit wraps Postgres PITR backup and recovery:
-
Real Application Testing on 🚀YugabyteDB with 🐘pgreplay
This blog was just to verify that it works with YugabyteDB. Check pgreplay documentation for more, all works the same in YugabyteDB. If you want to capture a workload from connections on multiple database nodes, each one will have their logfile. You can merge them. The Session ID (the 6th field in the csvlog built from start time and backend pid will probably not collide with another one, but you can make it unique by concatenating a node number if you want). The replay connects to one node, but though a HA proxy the connections can be distributed to multiple ones. All depends on what you want to capture and wh you want to replay. Capturing from PostgreSQL and replaying to YugabyteDB is also a good way to check that all works the same without performance regressions.
What are some alternatives?
docker-postgres-upgrade - a PoC for using "pg_upgrade" inside Docker -- learn from it, adapt it for your needs; don't expect it to work as-is!
Logidze - Database changes log for Rails
PostgreSQL-Disaster-Recovery-With-Barman - A complete end-end project that demonstrates the 'Traditional backup with WAL streaming' architecture implementation (Backup via rsync/SSH + WAL streaming). This is chosen as it provides incremental backup/restore & a bunch of other features.
aquameta - Web development platform built entirely in PostgreSQL
docker-pgautoupgrade - A PostgreSQL Docker container that automatically upgrades your database
blog - Subscribe to this repository to receive notifications whenever a new article is published at https://vb-consulting.github.io/
simonwillisonblog-backup - Backups of the database for simonwillison.net
temporal_tables - Postgresql temporal_tables extension in PL/pgSQL, without the need for external c extension.
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.