Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes
Date
Msg-id 16599.1281026992@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes  ("Chris" <christoph.springer@magicinternet.de>)
List pgsql-bugs
"Chris" <christoph.springer@magicinternet.de> writes:
> A Hot-Standby database is being backed up to a new machine like this:

> 0. pause WAL file deletion from Hot-Standby
> 1. backup pg_control
> 2. sync data and tablespace files
> 3. wait for checkout using pg_controldata and waiting for UNDO address
> change
> 4. copy all WAL files
> 5. recover the newly created database using WAL files

This process seems almost entirely unrelated to the documented way of
doing it; I'm not surprised that you end up with some files not in sync.
Please see pg_start_backup and friends.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Chris"
Date:
Subject: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #5599: Vacuum fails due to index corruption issues