pgBackRest
postgres
Our great sponsors
pgBackRest | postgres | |
---|---|---|
13 | 29 | |
2,145 | 2,064 | |
4.3% | 1.3% | |
9.2 | 7.8 | |
8 days ago | about 1 month ago | |
C | Shell | |
GNU General Public License v3.0 or later | MIT License |
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.
pgBackRest
-
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.
-
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?
-
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).
-
Backup Postgresql Docker
pgBackrest and barman can backup to S3
postgres
- How to Escape a Container
-
PyPI new user and new project registrations temporarily suspended
Tragedy of the commons - only need a few actors to ruin it all for us. Almost all distributors face this problem, from Docker Hub to PyPI. This also reminded me of official Postgres Docker image running a cryptominer in the background [1]
-
Nix Turns 20. What the Hell Is It?
If you open the dockerfile of the desired container, you can determine exactly how and what was built. If not satisfied, you can always build your own container with the right postgresql build flags.
-
How do I create a docker image for postgres with nix?
I got started on trying to make a basic postgres image but I can't seem to figure out how to include a shell script in the same folder as my nix file (fetched from https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh and to be modified once I get it working) into the docker image as an entrypoint
-
Awk: Power and Promise of a 40 yr old language (2021)
GNU awk and jq are at the heart of the templating engine used by a number of Docker Official Images:
https://github.com/docker-library/bashbrew/blob/master/scrip...
https://github.com/docker-library/postgres/blob/master/apply...
https://github.com/docker-library/postgres/blob/master/Docke...
-
understanding why some volumes populate and others dont
postgres file
postgres this link has the full dockerfile.
-
ubi8-init: Runtime configuration
Ok, so that link you sent mentions that the entrypoint.sh is from the official Postgres image. Well it looks like it is severely outdated.
-
how to mock DBs
The docker file I used is basically this one except as I mention I hack out the VOLUME line, which makes it transient.
-
Issues deploying Postgres onto K3s
I've been looking through bugs and error logs, and haven't been able to figure this out. I've tried the solutions suggested in https://github.com/docker-library/postgres/issues/116 by changing my data directory, which didn't work, tried messing with security context, which didn't work, and found setting the PV manually didn't work either.
What are some alternatives?
Barman - Barman - Backup and Recovery Manager for PostgreSQL
wal-g - Archival and Restoration for databases in the Cloud
docker-postgres-wale - Postgres docker container with WALE-E installed
wal-e - Continuous Archiving for Postgres
pghoard - PostgreSQL® backup and restore service
spilo - Highly available elephant herd: HA PostgreSQL cluster using Docker
checkmk - Checkmk - Best-in-class infrastructure & application monitoring
fpart - Sort files and pack them into partitions
MeshCentral - A complete web-based remote monitoring and management web site. Once setup you can install agents and perform remote desktop session to devices on the local network or over the Internet.
kanban-board - Single-click full-stack application (Postgres, Spring Boot & Angular) using Docker Compose
deck-chores - A job scheduler for Docker containers, configured via labels.