pgBackRest

Thank you @dataegret for your sponsorship of pgBackRest! Please consider a sponsorship if you use pgBackRest in your enterprise. github.com/sponsors/dwste…

A special thank you to @pgstef for sponsoring pgBackRest! Stefan has also been a contributor for many years. Please consider a sponsorship if you use pgBackRest in your enterprise. github.com/sponsors/dwste…

Many thanks to @supabase for their sponsorship! Please consider a sponsorship if you use pgBackRest in your enterprise. github.com/sponsors/dwste…

pgBackRest 2.58.0 released with object store improvements, TLS security enhancements, and the ability to manually expire the oldest backup. #2.58.0" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

@zemanekj @samokhvalov In our benchmarks TLS is generally about 50% faster than SSH. But I don't think that would hold here since the bottleneck is most likely elsewhere. Still, every little bit helps!

@samokhvalov Would be great to see TLS transfer method numbers. I guess it will perform better than SSH. But I admit that it will be more complex to set up.

#PostgresMarathon 2-012: Ultra-fast replica creation with pgBackRest postgres.ai/blog/20251105-… Couldn't believe the numbers: 35 TiB/h copying PGDATA from one EC2 instance to another. That's fast enough to clone a 10 TiB production database in ~17 minutes. Modern hardware + pgBackRest trick = game changer for zero-downtime operations at scale Credit: Maxim Boguk, Postgres expert I've known for years, who now helps the @postgres_ai team excel with really large systems [Chart showing throughput progression from 3.9 TiB/hour to 35+ TiB/hour when involving more processes]

pgBackRest 2.57.0 released with an option to suppress repository symlinks and bug fixes: #2.57.0" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…. Please consider a sponsorship if you use pgBackRest in your enterprise: github.com/sponsors/dwste….

pgBackRest 2.56.0 released with progress info improvements and bug fixes: #2.56.0" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…. Please consider a sponsorship if you use pgBackRest in your enterprise: github.com/sponsors/dwste….

@Cesar_DBA pgBackRest will warn you about corrupted pages if you have page checksums enabled in PostgreSQL and of course we have robust checksums to detect corruption at rest in the repository.

@pgBackRest when will we have recovery of corrupted pages or blocks? Will this feature be added someday? 🙃

@Cesar_DBA If you mean automatically fixing corrupted pages then this is not something we are planning to add to pgBackRest. Recovering from corruption is a complex process that depends greatly on the individual situation.

pgBackRest 2.55.0 released with PostgreSQL 18 support and many other bug fixes, improvements, and features. #2.55.0" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

pgBackRest 2.54.2 released with a fix for disabling bundling when block incremental has been enabled for prior backups. #2.54.2" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

pgBackRest 2.54.1 released with a fix for installations where pgBackRest does not have read access to pgbackrest.conf. #2.54.1" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

pgBackRest 2.54.0 released with support for recovering from accidental deletions or malware using versioned repositories, improved backup from standby, and more! #2.54.0" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

pgBackRest 2.53.1 released with support for PostgreSQL 17beta3 and bug fixes. #2.53.1" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

pgBackRest 2.53 released with support for concurrent cluster backups and other improvements. #2.53" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

pgBackRest 2.52.1 released with a bugfix: #2.52.1" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

pgBackRest 2.52 released with PostgreSQL 17 support, GCS batch delete, and S3 SSE-C encryption. #2.52" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

pgBackRest 2.51 released with a new meson build system and various improvements and bug fixes. #2.51" target="_blank" rel="nofollow noopener">pgbackrest.org/release.html#2…

@Percona In your example you have no backup on Sunday just so expire can run without conflict. Why miss a day of backup when you can just let expire run automatically after the full backup?

@Percona Second, running expire after backup does not make the backup run longer. The backup completes, then expire runs. This helps ensure that backup and expire do not overlap without needing to carefully schedule it.

pgBackRest simplifies the backup process in #PostgreSQL, but its default configuration often inefficiently combines backup and expiry together. Here, we show how to decouple backup and expiry operations. hubs.ly/Q02k9dJP0 #OpenSource #Percona