Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id BE610B5DC4C for ; Fri, 12 Aug 2011 10:39:39 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 34327-10 for ; Fri, 12 Aug 2011 13:39:33 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nm27-vm0.bullet.mail.ne1.yahoo.com (nm27-vm0.bullet.mail.ne1.yahoo.com [98.138.91.63]) by mail.postgresql.org (Postfix) with SMTP id 41D82B5DC44 for ; Fri, 12 Aug 2011 10:39:33 -0300 (ADT) Received: from [98.138.90.53] by nm27.bullet.mail.ne1.yahoo.com with NNFMP; 12 Aug 2011 13:39:32 -0000 Received: from [98.138.89.166] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 12 Aug 2011 13:39:32 -0000 Received: from [127.0.0.1] by omp1022.mail.ne1.yahoo.com with NNFMP; 12 Aug 2011 13:39:32 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 914542.72606.bm@omp1022.mail.ne1.yahoo.com Received: (qmail 19314 invoked by uid 60001); 12 Aug 2011 13:39:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1313156372; bh=4sYpnnSu7Gk6mZVOQse8+LZqRyeORD6zzwzie2H2eco=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=WvJW5BV4R7MA9BJqL1xkQh8uWLjU7BhDIN7nivCeDrVuqbGDLmvQsD/q1tRX7Lg4dO7W9mb5V8n0kFnC+f0asl1j0To5eJ6k5SwLoK1kDTNST3SCmCb4jKnC4zrR2fP/wJp+gfXP+vlbZLDAlGcpkkSn6GEA/4w5uLGij1M8JJA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=xx6VNBbEF/UCslZy24DmfVQW2jhRbs/Ai6SHEREey4kqbsqKZVkJ5I/DYC06mx57XCm8pp5OU+IgHfGBIJicoN6Lvnm4t38yWe/x90/z5BRYVgrdjO2SBjK1tJYT8WgP2kTSZF8EFeFc+zU2hBzBVbLKONhjRYqmlPzBqYD/ziQ=; X-YMail-OSG: ZGt.bS4VM1lqHZEj327OxbwXeczKy098cNc4ilcFdkSSuks nWdzdNYMAKu2FG5x_._xz5IGsx.OkdLAPi4nZr.G7GQ96r3INr7spKbdmJpQ Nzz7IlvU7Q1X3fzmbeF3fBItgr7hKL6lawRL3niB1xeG60KMVeKB5da6Tpcg .KstVDHp5shmsxItO9U82eAjMRzgupWBv668ClUgl3fH0Gg.r1INkVmGZOvE 1JE.aWDQu.PI8w4klqsREknWC4XF_IN_hVIVG6H7hrpkpxPJzptZQ8VZMje. vNRE6g1swH.xQe5ghGDiOe7qvClIzj1aMSpA7lICaOm.vkYGZOIA91kG1uXT FDKpW67BB54TQyYO1C0fknLhK.QtiT4GL Received: from [64.61.91.74] by web120002.mail.ne1.yahoo.com via HTTP; Fri, 12 Aug 2011 06:39:32 PDT X-Mailer: YahooMailWebService/0.8.113.313619 Message-ID: <1313156372.66476.YahooMailNeo@web120002.mail.ne1.yahoo.com> Date: Fri, 12 Aug 2011 06:39:32 -0700 (PDT) From: A J Reply-To: A J Subject: How to remove index from memory ? To: PG Admin MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-299933220-91286296-1313156372=:66476" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.709 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.811 X-Spam-Level: X-Archive-Number: 201108/114 X-Sequence-Number: 38101 ---299933220-91286296-1313156372=:66476 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hello=0AI am running a test to find the impact of corrupt indexes on querie= s. I corrupted the index file but observed that the queries continued to pe= rform without issues. It was only on restart of the database that postgres = realized that the indexes are corrupt and my queries started failing (with = error like:=A0ERROR:=A0 invalid page header in block 0 of relation base/163= 84/16399)=0A=0AMy questions are:=0A1. How do I remove the indexes from memo= ry ? I wish to stimulate the condition when indexes are no longer in databa= se but the server has not restarted and see the effects of corrupt indexes.= =0A2. Is there a more proactive and realtime way to detect corruption of in= dexes ?=0A=0AThanks for any inputs. ---299933220-91286296-1313156372=:66476 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hello=
I am running a test to find the impact of corrupt ind= exes on queries. I corrupted the index file but observed that the queries c= ontinued to perform without issues. It was only on restart of the database = that postgres realized that the indexes are corrupt and my queries started = failing (with error like: ERROR:  invalid page = header in block 0 of relation base/16384/16399)

My questions are:
1. How= do I remove the indexes from memory ? I wish to stimulate the condition wh= en indexes are no longer in database but the server has not restarted and s= ee the effects of corrupt indexes.
2. Is there a more proactiv= e and realtime way to detect corruption of indexes ?

Thanks for any inputs.
---299933220-91286296-1313156372=:66476--