lz4-conduit
pgBackRest
Our great sponsors
| lz4-conduit | pgBackRest | |
|---|---|---|
| - | 13 | |
| 2 | 2,209 | |
| - | 5.1% | |
| 0.0 | 9.2 | |
| about 6 years ago | 2 days ago | |
| C | C | |
| BSD 3-clause "New" or "Revised" 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.
lz4-conduit
We haven't tracked posts mentioning lz4-conduit yet.
Tracking mentions began in Dec 2020.
pgBackRest
-
pgBackRest: PostgreSQL S3 backups
This tutorial explains how to backup PostgreSQL database using pgBackRest and S3.
-
Anything can be a message queue if you use it wrongly enough
This isn't theoretical; many companies do PostgreSQL async 1:N physical replication, by using e.g. https://pgbackrest.org/ to have the primary push WAL segment files (a.k.a. "the last n milliseconds of packets" in the write-ahead log) as objects to S3, and then to have all read-replicas fetch from S3 and replay.
> You could do even better if you out-of-band signal the readiness so you do not need to poll while idle.
S3 and its clones have "object lifecycle notifications", where you can be informed by a push-based mechanism whenever a new object is put into the bucket.
But — what do you have to do, to get these notifications?
Subscribe to a message queue that S3 puts them into.
-
Kubernetes postgres backups
I haven't explored the territory in awhile but for bare-metal, you can't go wrong with Percona Distribution, which includes pgBackRest and a minimal web-ui. No one ever got fired for using Percona, etc.
- pgBackRest - Reliable PostgreSQL Backup & Restore
- pgBackRest - have you used it and what was your experience?
-
How to backup database
Check out pgBackRest
-
Use One Big Server
I found this approach pretty cool in that regard: https://github.com/pgbackrest/pgbackrest
- Moving from Oracle to Postgres, what should I know?
-
How do you back up your databases?
Something like PG barman or pg backrest could be good for you on the Postgres side.
-
Cloud SQL is not great
Backups are limited. These days, pgbackrest is the go-to backup solution for PostgreSQL, and having used it I am very impressed so far. It provides full backups, differential, and incremental, as well as archiving of WAL segments for point in time recovery. It allows great flexibility in schedules and destinations for backups, how long to keep backups for, how many full backups. For example, you can have backups made to a local disk, and other backups to an external S3-compatible bucket, each with their own settings and schedules (e.g., scheduled via cron).
What are some alternatives?
lizard - A simple code complexity analyser without caring about the C/C++ header files or Java imports, supports most of the popular languages.
Barman - Barman - Backup and Recovery Manager for PostgreSQL
TurboBench - Compression Benchmark
wal-g - Archival and Restoration for databases in the Cloud
7-Zip-zstd - 7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard
docker-postgres-wale - Postgres docker container with WALE-E installed
p7zip - A new p7zip fork with additional codecs and improvements (forked from https://sourceforge.net/projects/sevenzip/ AND https://sourceforge.net/projects/p7zip/).
wal-e - Continuous Archiving for Postgres
LZ4 - Extremely Fast Compression algorithm
pghoard - PostgreSQL® backup and restore service
postgres - Docker Official Image packaging for Postgres
spilo - Highly available elephant herd: HA PostgreSQL cluster using Docker