pgBackRest

Reliable PostgreSQL backup and restore solution that will seamlessly scale up to the largest databases and workloads.

[pgBackRest @pgBackRest]

pgBackRest will continue! https://t.co/cTc2ry6Qjj

[pgBackRest @pgBackRest]

UPDATE: pgBackRest is likely to receive enough funding be be revived. See https://t.co/w9xHam9Ava for details.

[pgBackRest @pgBackRest]

TL;DR: pgBackRest is no longer being maintained. For details see https://t.co/w9xHam9Ava

[pgBackRest @pgBackRest]

Thank you @dataegret for your sponsorship of pgBackRest! Please consider a sponsorship if you use pgBackRest in your enterprise. https://t.co/rAh2Q3yI3q

[pgBackRest @pgBackRest]

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. https://t.co/rAh2Q3yI3q

[pgBackRest @pgBackRest]

Many thanks to @supabase for their sponsorship! Please consider a sponsorship if you use pgBackRest in your enterprise. https://t.co/rAh2Q3yI3q

[pgBackRest @pgBackRest]

pgBackRest 2.58.0 released with object store improvements, TLS security enhancements, and the ability to manually expire the oldest backup. https://t.co/qOPridfGzh

[pgBackRest @pgBackRest]

@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!

[pgBackRest @pgBackRest]

pgBackRest 2.57.0 released with an option to suppress repository symlinks and bug fixes: https://t.co/3jGmrSryei. Please consider a sponsorship if you use pgBackRest in your enterprise: https://t.co/rAh2Q3yI3q.

[pgBackRest @pgBackRest]

pgBackRest 2.56.0 released with progress info improvements and bug fixes: https://t.co/CsFp5qA3uX. Please consider a sponsorship if you use pgBackRest in your enterprise: https://t.co/rAh2Q3yadS.

[pgBackRest @pgBackRest]

@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 @pgBackRest]

@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 @pgBackRest]

pgBackRest 2.55.0 released with PostgreSQL 18 support and many other bug fixes, improvements, and features. https://t.co/rQuCohAwNo

[pgBackRest @pgBackRest]

pgBackRest 2.54.2 released with a fix for disabling bundling when block incremental has been enabled for prior backups. https://t.co/cWOHlhwbZm

[pgBackRest @pgBackRest]

pgBackRest 2.54.1 released with a fix for installations where pgBackRest does not have read access to pgbackrest.conf. https://t.co/hO4LpBdsFH

[pgBackRest @pgBackRest]

pgBackRest 2.54.0 released with support for recovering from accidental deletions or malware using versioned repositories, improved backup from standby, and more! https://t.co/N74Z0LixfN

[pgBackRest @pgBackRest]

pgBackRest 2.53.1 released with support for PostgreSQL 17beta3 and bug fixes. https://t.co/9yyK5gPtgG

[pgBackRest @pgBackRest]

pgBackRest 2.53 released with support for concurrent cluster backups and other improvements. https://t.co/sCKmPKeG5Y

[pgBackRest @pgBackRest]

pgBackRest 2.52.1 released with a bugfix: https://t.co/3A9lO1ZSM8

[pgBackRest @pgBackRest]

pgBackRest 2.52 released with PostgreSQL 17 support, GCS batch delete, and S3 SSE-C encryption. https://t.co/n9hw7kjevT