pgBackRest
pg_wait_sampling
Our great sponsors
pgBackRest | pg_wait_sampling | |
---|---|---|
13 | 3 | |
2,177 | 132 | |
3.7% | 0.8% | |
9.2 | 5.6 | |
5 days ago | 5 months ago | |
C | C | |
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.
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
pg_wait_sampling
-
Moving from Oracle to Postgres, what should I know?
pg_wait_sampling together with pg_stat_statements gets you nearer to Oracle's ASH/AWR capabilities. PoWA can integrate that (and other interesting extensions) to generate some nice reports.
-
[RDS] Huge spikes in CPU Usage, but the Freeable Memory remains high. How do I configure my DB to use more memory?
Another Another source of high CPU could be wait events. There are no built-in tools in Postgres to monitor them (unless RDS provides some). The approach I'd take on a "regular" Postgres installation is to sample the content of pg_stat_activity and then later analyze that after spikes have occurred. There are several extensions that already provide this, e.g. pg_profile or pg_wait_sampling or pgsentinel
-
Any Tips for Analyzing (Concurrent) Transaction Performance?
pg_wait_sampling
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
postgres - Docker Official Image packaging for Postgres
spilo - Highly available elephant herd: HA PostgreSQL cluster using Docker
pg_profile - Postgres historic workload reports
fpart - Sort files and pack them into partitions
pg_show_plans - Show query plans of all currently running SQL statements
pgsentinel - postgresql extension providing Active session history
IvorySQL - Open Source Oracle Compatible PostgreSQL.