Re: Corrupt RTREE index - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Corrupt RTREE index
Date
Msg-id 1103055179.22049.25.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: Corrupt RTREE index  ("Dann Corbit" <DCorbit@connx.com>)
Responses Re: Corrupt RTREE index  (Neil Conway <neilc@samurai.com>)
Re: Corrupt RTREE index  (Greg Stark <gsstark@mit.edu>)
List pgsql-general
IS this same issue true for hash or GiST indexes?

On Tue, 2004-12-14 at 13:49, Dann Corbit wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
>                http://archives.postgresql.org

pgsql-general by date:

Previous
From: Richard_D_Levine@raytheon.com
Date:
Subject: Re: Best practice in postgres
Next
From: "Jimmie H. Apsey"
Date:
Subject: Re: Performance differences 7.1 to 7.3