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

From valgog
Subject Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes
Date
Msg-id 0f40d3e6-352e-4d53-9ba3-f64f535040d4@u26g2000yqu.googlegroups.com
Whole thread Raw
In response to BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes  ("Chris" <christoph.springer@magicinternet.de>)
Responses Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-bugs
> 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.
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 regards, tom lane
>

Hallo Tom,

It was done as documented in http://www.postgresql.org/docs/9.0/static/back=
up-incremental-updated.html

With my best regards,

-- Valentine

pgsql-bugs by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: [HACKERS] Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by)
Next
From: Josh Berkus
Date:
Subject: Re: [HACKERS] Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by)