Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U0ECI-0000RF-Bu for pgsql-admin@arkaria.postgresql.org; Tue, 29 Jan 2013 16:38:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1U0ECH-0002xy-SO for pgsql-admin@arkaria.postgresql.org; Tue, 29 Jan 2013 16:38:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U0ECG-0002x3-IH for pgsql-admin@postgresql.org; Tue, 29 Jan 2013 16:38:08 +0000 Received: from smtp-outbound-1.vmware.com ([208.91.2.12]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U0ECE-0005Ai-Da for pgsql-admin@postgresql.org; Tue, 29 Jan 2013 16:38:08 +0000 Received: from sc9-mailhost2.vmware.com (sc9-mailhost2.vmware.com [10.113.161.72]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id A599F283C4; Tue, 29 Jan 2013 08:38:05 -0800 (PST) Received: from zcs-prod-ext-mta-2.vmware.com (zcs-prod-ext-mta-2.vmware.com [10.113.62.224]) by sc9-mailhost2.vmware.com (Postfix) with ESMTP id A2E29B04F1; Tue, 29 Jan 2013 08:38:05 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs-prod-ext-mta-2.vmware.com (Postfix) with ESMTP id 57C5CC1595; Tue, 29 Jan 2013 08:38:05 -0800 (PST) X-Virus-Scanned: amavisd-new at zcs-prod-ext-mta-2.vmware.com Received: from zcs-prod-ext-mta-2.vmware.com ([127.0.0.1]) by localhost (zcs-prod-ext-mta-2.vmware.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BUwNMacuM2jD; Tue, 29 Jan 2013 08:38:05 -0800 (PST) Received: from zcs-prod-ext-mta-2.vmware.com (localhost.localdomain [127.0.0.1]) by zcs-prod-ext-mta-2.vmware.com (Postfix) with ESMTP id 2FED7C158E; Tue, 29 Jan 2013 08:38:05 -0800 (PST) Received: from [192.168.1.90] (unknown [10.113.62.14]) by zcs-prod-ext-mta-2.vmware.com (Postfix) with ESMTPSA; Tue, 29 Jan 2013 08:38:04 -0800 (PST) Message-ID: <5107FAFA.4020305@vmware.com> Date: Tue, 29 Jan 2013 18:38:18 +0200 From: Heikki Linnakangas 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 CC: pgsql-admin@postgresql.org Subject: Re: corrupted indexes when using base backups generated from hot standby References: <50F53613.6000702@vmware.com> <5107F9B6.8060903@vmware.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -7.4 (-------) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 29.01.2013 18:36, Lonni J Friedman wrote: > On Tue, Jan 29, 2013 at 8:32 AM, Heikki Linnakangas > wrote: >> 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? > > Sorry, I don't understand what you're requesting. How can I reduce a > test case when all I'm doing to generate the corrupted data is running > pg_basebackup on the standby? Do you mean using a smaller database? Yes, smaller database, and a simpler schema with e.g only one table and index. And only do inserts while the backup is running, for example. - Heikki -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin