Company database holding critical data goes down after a hard disk crash. There is no redundancy, and no usable backups. The only thing that remains is just a list of files with no structure, recovered from the destroyed filesystem. There is intense time pressure to get back online, and no clear path forward.
This is the true story of a remarkable data recovery, and how PostgreSQL's resilience and clean design made it possible. We will walk through every step, including dealing with lost files and some of the shortcuts taken.
Recovering from Data Loss Despite Not Having a Backup: A Postgres True Story - Talk given at the Southern California Linux Expo (SCaLE 21x), Pasadena, CA
Most of Britain's primary schools have reopened their doors this morning, while secondary school students will…
Please join us for a discussion on the Export-Import Bank's contribution to the U.S. economy,…
Bank Of England Sends Bail In Paperwork Neil's Weekly NEWS! ⬇️ NMW 'Approved' Services: ⬇️…
The Bank of Canada is holding its key interest rate steady for the first time…