Re: Corrupt RTREE index - Mailing list pgsql-general

From Dann Corbit
Subject Re: Corrupt RTREE index
Date
Msg-id D425483C2C5C9F49B5B7A41F8944154705572A@postal.corporate.connx.com
Whole thread Raw
In response to Corrupt RTREE index  (Greg Stark <gsstark@mit.edu>)
Responses Re: Corrupt RTREE index  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-general
I suggest a warning (if there is not already one generated) on create
index for rtree indexes so that users know that they are not fully
supported.

-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Monday, December 13, 2004 4:14 PM
To: Greg Stark
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Corrupt RTREE index

Greg Stark <gsstark@mit.edu> writes:
> So you don't think this case is worth doing forensics on?

If the problem goes away after REINDEX then I'll write it off as missing
WAL support.  rtree is not high enough on my list of priorities to
justify more effort :-(

            regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org

pgsql-general by date:

Previous
From: Együd Csaba
Date:
Subject: Deadlock detected during vacuum analyze
Next
From: Richard_D_Levine@raytheon.com
Date:
Subject: Re: Best practice in postgres