Re: Incorrect behaviour when using a GiST index on points - Mailing list pgsql-hackers

From Noah Misch
Subject Re: Incorrect behaviour when using a GiST index on points
Date
Msg-id 20121023163515.GA18141@tornado.leadboat.com
Whole thread Raw
In response to Re: Incorrect behaviour when using a GiST index on points  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Tue, Oct 23, 2012 at 11:18:48AM -0300, Alvaro Herrera wrote:
> Please see downthread -- there is some commentary from Noah ([1] and
> others) about the patch itself.  As far I understand, some changes are
> still needed, and I don't know if the last version submitted is the
> version that should be backpatched.

We'd best use the same patch for both HEAD and back branches; pg_upgrade would
carry forward faulty indexes.  pg_upgrade could instead invalidate them, but I
don't think the gravity of the problem calls for it.  A release note
suggesting a REINDEX of affected indexes ought to suffice.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: "pg_ctl promote" exit status
Next
From: Robert Haas
Date:
Subject: Re: [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility