Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 01B8BB5DBE5 for ; Thu, 18 Aug 2011 18:46:13 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 66647-01 for ; Thu, 18 Aug 2011 21:46:06 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nm13-vm0.bullet.mail.ne1.yahoo.com (nm13-vm0.bullet.mail.ne1.yahoo.com [98.138.91.48]) by mail.postgresql.org (Postfix) with SMTP id A381AB5D803 for ; Thu, 18 Aug 2011 18:46:05 -0300 (ADT) Received: from [98.138.90.51] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 18 Aug 2011 21:46:04 -0000 Received: from [98.138.86.157] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 18 Aug 2011 21:46:04 -0000 Received: from [127.0.0.1] by omp1015.mail.ne1.yahoo.com with NNFMP; 18 Aug 2011 21:46:04 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 887485.77200.bm@omp1015.mail.ne1.yahoo.com Received: (qmail 61908 invoked by uid 60001); 18 Aug 2011 21:46:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1313703964; bh=eh688cVWP41Xj1aCGztsn3fyhQOkJFR4GGFLSkOS5tw=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=VULPGbzzF/+uMwJ3dDfejMo0Q/q6xEtTFfV5CRnKn+NDxObXnGH/OcsiNdLxvvaRHwkY8DTBSz6D8KiJCQVWmDUKSyPKw5jzAFZXKjO3iEmiZhd037i0gJpWR/uYJ+IDJSvNEQQcHF8KdYg8875SJLtdPpNzgfen1z2zcEewEOc= 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=Fjsr7m1o+v0VLOfApnsPE4p4iEDDeN92dzf0NRJCksYpBQhXAmdfkiNEL3q6Ga6FkPtUZy3mm6E+P+syKOtPDEXcC56adl+OtOy2HRMbwA34BmmGOjxgi1wVexE6HS5gIB152EUbi/QQyUHU59w6otiFHg07iDI0WJIT1TPK058=; X-YMail-OSG: bLIU_7QVM1lij.rpHFp4XiZHiblBAxkOqeo4JcrZ_BkzM1C bjAlXxtj4.TC.DixfOh0Z50TWU2Eg.qqisxdJpNdonxvWsu8iZq8YOVOkl_1 6asdR7SOJjLnv3xyk8VQRMaPwJDnz0zVGwYPJsdFPlSqYmOcCJnm5AqTTquc iCL08uU10dmb2MInc.D3mt4jvlJkyOBT8iKKzvC59j1phP3LNeN4DJhBtn3p 4_FIHo2fHGhkA2cDmHZLrJkJxpxCF1MsmguhvhlwH0GDyAouuQ_CLTRFTt5_ mkYIROyFiO0y410Uonxk2pj85wHksAQkUnhfdFxKD3b6if8_nMqYpglBNO74 zcLbwTz6s282eXnnVDjrJ40ImStl.3YgY Received: from [64.61.91.74] by web120001.mail.ne1.yahoo.com via HTTP; Thu, 18 Aug 2011 14:46:04 PDT X-Mailer: YahooMailWebService/0.8.113.313619 Message-ID: <1313703964.54877.YahooMailNeo@web120001.mail.ne1.yahoo.com> Date: Thu, 18 Aug 2011 14:46:04 -0700 (PDT) From: A J Reply-To: A J Subject: Question on Postgres Index internals To: PG Admin MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-134638194-465438361-1313703964=:54877" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.166 tagged_above=-10 required=5 tests=BAYES_20=-0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.167 X-Spam-Level: X-Archive-Number: 201108/174 X-Sequence-Number: 38161 ---134638194-465438361-1313703964=:54877 Content-Type: text/plain; charset=us-ascii How does Postgres detect corruption of index data files ? What is the exact mechanism by which it knows that the index is corrupt ? Can it happen that part of the index is corrupt but Postgres does not realize because those specific rows are not accessed (but other rows from that table are accessed) Thanks for any inputs. ---134638194-465438361-1313703964=:54877 Content-Type: text/html; charset=us-ascii
How does Postgres detect corruption of index data files ? What is the exact mechanism by which it knows that the index is corrupt ? Can it happen that part of the index is corrupt but Postgres does not realize because those specific rows are not accessed (but other rows from that table are accessed)

Thanks for any inputs.
---134638194-465438361-1313703964=:54877--