Re: SPGist "triple parity" concept doesn't work

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgreSQL(dot)org, hailong(dot)li(at)qunar(dot)com
Subject: Re: SPGist "triple parity" concept doesn't work
Date: 2013-06-07 17:11:41
Message-ID: 20130607171141.GF4407@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2013-06-07 17:33:17 Re: ALTER DEFAULT PRIVILEGES FOR ROLE is broken
Previous Message Fred&Dani&Pandora&Aquiles 2013-06-07 17:09:57 Parallell Optimizer