Corruption detection

From PostgreSQL wiki

Revision as of 12:53, 4 March 2013 by Ringerc (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

If you think you might be suffering database corruption you're in the wrong place. Read and act on the Corruption article.

Contents

Introduction

Detecting storage layer corruption inside PostgreSQL as early as possible is important. If left undetected, it could not only lead to wrong answers, it can also end up being copied during a base backup (affecting backups and replication). That is a major problem because users will get a false sense of confidence relying on their backup schedule.

If you think you might be suffering database corruption you're in the wrong place. Read and act on the Corruption article.

An article about steps to avoid and prevent database corruption can be found here.

Types of Corruption

Theoretically, corruption can happen in many areas of hardware, including the memory or even the CPU. However, for this article we focus on corruption happening between the time a page leaves the address space of the backend process until the time it is read back in.

Minor Challenges

Utilities and Background Checking

Utilities (such as pg_basebackup) should be updated to verify pages while creating the backup. Also, users might want a continuously-running daemon to slowly validate cold data.

Detecting Transposed Data

Zero Pages

Major Challenges

Upgrade and On/Off

Torn Pages

Personal tools