Thank you @dataegret for your sponsorship of pgBackRest! Please consider a sponsorship if you use pgBackRest in your enterprise. https://t.co/rAh2Q3yI3q
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 2.58.0 released with object store improvements, TLS security enhancements, and the ability to manually expire the oldest backup. https://t.co/qOPridfGzh
@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 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 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.
@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.
@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.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