Re: Corrupt RTREE index

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Dann Corbit <DCorbit(at)connx(dot)com>
Cc: pgsql-hackers-owner(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: Corrupt RTREE index
Date: 2004-12-14 20:12:59
Message-ID: 1103055179.22049.25.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: Monday, December 13, 2004 4:14 PM
> To: Greg Stark
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Corrupt RTREE index
>
> Greg Stark <gsstark(at)mit(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mike Cox 2004-12-14 20:20:07 4th RFD: comp.databases.postgresql
Previous Message Richard_D_Levine 2004-12-14 19:55:19 Re: Best practice in postgres