From 1d31908b1e0aef7e450c8a92f0666c5e99a826bd Mon Sep 17 00:00:00 2001 From: Grigory Smolkin Date: Sat, 20 Apr 2019 00:42:59 +0300 Subject: [PATCH] README: add checkdb --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index e2b11b83..391ab1d0 100644 --- a/README.md +++ b/README.md @@ -18,6 +18,7 @@ As compared to other backup solutions, `pg_probackup` offers the following benef * Custom commands to simplify WAL log archiving * External to PGDATA directories, such as directories with config files and scripts, can be included in backup * Remote backup, restore, archive-push and archive-get operations via ssh (beta) +* Checking running PostgreSQL instance for the sights of corruption in read-only mode via `checkdb` command. To manage backup data, `pg_probackup` creates a backup catalog. This directory stores all backup files with additional meta information, as well as WAL archives required for [point-in-time recovery](https://postgrespro.com/docs/postgresql/current/continuous-archiving.html). You can store backups for different instances in separate subdirectories of a single backup catalog.