Avoiding, Detecting, and Recovering From Data Corruption
Avoiding, Detecting, and Recovering From Data Corruption
Schedule

Presented by:

43e7696a35a5a4451a9a2ad8fe270fe6

Robert Haas

from EnterpriseDB

Robert Haas is a PostgreSQL major contributor and committer. PostgreSQL features which he has authored or coauthored include unlogged tables, fast-path locking, index-only scans, and parallel query. PostgreSQL features written by others which he has reviewed and committed include partitioning, logical decoding, event triggers, and foreign tables. He works at EnterpriseDB as VP, Chief Database Scientist.

Checkout the slides

Hardware or software failure or user error can result in your PostgreSQL database becoming corrupted. In this talk, I'll discuss some things that you can do to minimize the likelihood that your database will become corrupted. In case that doesn't work, or you already have a corrupted database, I'll also discuss signs you may be able to spot that will tell you that your database has become corrupted, and some techniques you can use to try to recover as much of your data as possible.

Date:
2020 February 27 - 11:00
Duration:
40 min
Room:
Grand Victoria 1
Conference:
PGConf India, 2020
Language:
Track:
Database Administration
Difficulty:
Medium

Happening at the same time:

  1. Taming 100+ PostgreSQL instances on the Cloud
    2. Start Time:
    2020 February 27 11:00

    Room:
    Robusta + Arabica

  2. Full Text Search in PG12
    3. Start Time:
    2020 February 27 11:00

    Room:
    Grand Victoria 2