Message-ID: <5107F9B6.8060903@vmware.com>
Date: Tue, 29 Jan 2013 18:32:54 +0200
From: Heikki Linnakangas <hlinnakangas@vmware.com>
Organization: VMware
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Lonni J Friedman <netllama@gmail.com>
CC: pgsql-admin@postgresql.org
Subject: Re: corrupted indexes when using base backups generated from hot
	standby
References: 
 <CAP=oouE5niXgAO_34Q+FGq=tS6EsMHXXRRoByov3zn9pU4249w@mail.gmail.com>
	<50F53613.6000702@vmware.com>
	<CAP=oouGKgRizsK-z8FRnFSJrmWbpsx=N+Me6YHnZvD0TKND6aQ@mail.gmail.com>
In-Reply-To: 
 <CAP=oouGKgRizsK-z8FRnFSJrmWbpsx=N+Me6YHnZvD0TKND6aQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 26.01.2013 01:28, Lonni J Friedman wrote:
> On Tue, Jan 15, 2013 at 2:57 AM, Heikki Linnakangas
> <hlinnakangas@vmware.com>  wrote:
>> That process sounds correct. Since you're using pg_basebackup -x option, you
>> don't even need to copy the WAL logs, although it shouldn't do any harm
>> either . The tar file should contain everything needed to restore the
>> backup.
>>
>> Can you provide more information? The log output would be nice. How large is
>> the database? What kind of activity is there in the master while the backup
>> is taken?
>
> Sorry for the delayed reply, I was out of the office.
>
> The database is about 530GB uncompressed.  The master is quite busy
> all the time, with inserts, updates&  deletes.
>
> I've attached all the recent errors.  I could send you the entire log
> if you'd prefer, its about 800KB compressed.

Thanks. I'm afraid I didn't get any wiser from the log output. Since 
this is a test system, could you reduce the test case into something 
smaller and self-contained?

- Heikki


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin