Re: SPGist "triple parity" concept doesn't work - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: SPGist "triple parity" concept doesn't work
Date
Msg-id 20130607171141.GF4407@eldon.alvh.no-ip.org
Whole thread Raw
In response to SPGist "triple parity" concept doesn't work  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SPGist "triple parity" concept doesn't work
List pgsql-hackers
Tom Lane wrote:

> I don't immediately see any good way to fix this.  I think the "triple
> parity" rule as it stands is hopelessly broken, but I don't know what
> to replace it with, even granting that we don't need to maintain on-disk
> compatibility.  (We'd have to tell people to reindex SPGist indexes
> anyway, because of the risk that they already contain circular links;
> so switching to a new layout rule doesn't seem to add any more pain.)
> Or we could try to modify the insertion algorithm so it doesn't lock
> two levels of the tree at once, but that seems pretty risky.

Is this the chance to add a metapage?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ALTER DEFAULT PRIVILEGES FOR ROLE is broken
Next
From: "Fred&Dani&Pandora&Aquiles"
Date:
Subject: Parallell Optimizer