From da8b337ee80b7c28ffb8fde7a4b0a11418b926c8 Mon Sep 17 00:00:00 2001 From: David Steele Date: Tue, 16 Jun 2015 15:44:27 -0400 Subject: [PATCH] Added supported versions of PostreSQL. --- README.md | 3 ++- doc/doc.xml | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ab763c019..9ad595c41 100644 --- a/README.md +++ b/README.md @@ -13,11 +13,12 @@ Primary PgBackRest features: - In-stream compression/decompression - Archiving and retrieval of logs for replicas/restores built in - Async archiving for very busy systems (including space limits) -- Backup directories are consistent Postgres clusters (when hardlinks are on and compression is off) +- Backup directories are consistent PostgreSQL clusters (when hardlinks are on and compression is off) - Tablespace support - Restore delta option - Restore using timestamp/size or checksum - Restore remapping base/tablespaces +- Support for PostgreSQL >= 8.3 Instead of relying on traditional backup tools like tar and rsync, PgBackRest implements all backup features internally and uses a custom protocol for communicating with remote systems. Removing reliance on tar and rsync allows for better solutions to database-specific backup issues. The custom remote protocol limits the types of connections that are required to perform a backup which increases security. diff --git a/doc/doc.xml b/doc/doc.xml index 71af4171e..c1ee35581 100644 --- a/doc/doc.xml +++ b/doc/doc.xml @@ -15,11 +15,12 @@
  • In-stream compression/decompression
  • Archiving and retrieval of logs for replicas/restores built in
  • Async archiving for very busy systems (including space limits)
  • -
  • Backup directories are consistent Postgres clusters (when hardlinks are on and compression is off)
  • +
  • Backup directories are consistent clusters (when hardlinks are on and compression is off)
  • Tablespace support
  • Restore delta option
  • Restore using timestamp/size or checksum
  • Restore remapping base/tablespaces
  • +
  • Support for >= 8.3
  • Instead of relying on traditional backup tools like tar and rsync, implements all backup features internally and uses a custom protocol for communicating with remote systems. Removing reliance on tar and rsync allows for better solutions to database-specific backup issues. The custom remote protocol limits the types of connections that are required to perform a backup which increases security.