Re: How safe is pg_basebackup + continuous archiving?

From: Kaixi Luo <kaixiluo(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: How safe is pg_basebackup + continuous archiving?
Date: 2016-06-30 12:00:16
Message-ID: CAHo5iyjMYRdc4DEg6Mz6-WGP2OCZ9CfEydgoa9GetC_ZoCg2Kg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> Before replaying a backup on a production system, you would need a
> pre-production setup where the backup is replayed and checked.
> Honestly, you can only be sure that a backup is working correctly
> after reusing it. You could always do some validation of the raw
> backup contents, but you need at the end the WAL applied on top of it
> to be able to check the status of a server that has reached a
> consistent point.
>

Could you elaborate a bit more on this last part? If a PostgreSQL recovery
from a pg_basebackup reaches a consistent point and is able to start up
fully, that is not a guarantee that there hasn't been any underlying
corruption, as far as I know. Am I correct on this?

Thanks once again.

Kaixi

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mike Sofen 2016-06-30 12:42:02 Re: Stored procedure version control
Previous Message Chris Lewis 2016-06-30 10:53:24 Log archiving failing. Seems to be wrong timeline