Skip site navigation (1) Skip section navigation (2)

Re: Indexes getting corrupted.

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruno G(dot) Albuquerque" <balbuquerque(at)dba(dot)com(dot)br>,Scott Marlowe <smarlowe(at)g2switchworks(dot)com>,pgsql-admin(at)postgresql(dot)org
Subject: Re: Indexes getting corrupted.
Date: 2005-06-16 09:05:41
Message-ID: 1118912741.3645.206.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On Fri, 2005-06-10 at 12:57 -0400, Tom Lane wrote:
> "Bruno G. Albuquerque" <balbuquerque(at)dba(dot)com(dot)br> writes:
> > Any pointers? Is there anything I can do for Windows to actually wait 
> > for the postgresql processes to clean up?
> What it looks like to me is that your disk drive is lying about what
> it's actually written; or possibly Windows is lying to Postgres about
> what it's actually written.  The former is pretty common and can usually
> be fixed by turning off write caching.

Possibly. But why would this effect only indexes?

This is the same error that was also reported on GENERAL recently on

I'm suspicious of a more subtle intermittent error. We have no
information about what the magic values are, only that they are not
correct. Should we increase the information returned for that error?
That might show up an error cause.

Best Regards, Simon Riggs

Attachment: btmetainfo.patch
Description: text/x-patch (2.5 KB)

In response to


pgsql-admin by date

Next:From: Stefan BayerDate: 2005-06-16 09:41:00
Subject: WindowsXP setup user account problem
Previous:From: Bill HernandezDate: 2005-06-16 04:58:11
Subject: $_SERVER['SERVER_ADDR'] ; returns wrong value "::1"

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group