Re: Corrupt RTREE index

From: "Dann Corbit" <DCorbit(at)connx(dot)com>
To: <pgsql-hackers-owner(at)postgresql(dot)org>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Corrupt RTREE index
Date: 2004-12-14 19:49:21
Message-ID: D425483C2C5C9F49B5B7A41F8944154705572A@postal.corporate.connx.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard_D_Levine 2004-12-14 19:55:19 Re: Best practice in postgres
Previous Message Együd Csaba 2004-12-14 19:23:21 Deadlock detected during vacuum analyze