Re: "Value locking" Wiki page - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: "Value locking" Wiki page
Date
Msg-id 542BDE3C.7040802@vmware.com
Whole thread Raw
In response to Re: "Value locking" Wiki page  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: "Value locking" Wiki page
List pgsql-hackers
On 10/01/2014 01:50 PM, Simon Riggs wrote:
> On 1 October 2014 10:44, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
>
>> I didn't realize that "promise index tuples" were even seriously discussed.
>> I guess that can be made to work, too, although I don't see the point. It
>> wouldn't work with GiST indexes, for the same reasons as page-level locking
>> won't work (a tuple can legally be inserted anywhere in a GiST index - it
>> just degrades the index making searching more expensive). And lossy GiST
>> opclasses are a problem too.
>
> GiST doesn't support unique indexes, so it is not in any way a problem.

GiST supports exclusion constraints. That is one of the main reasons I 
want to do promise tuples, instead of locking within the indexam: to 
support this feature with exclusion constraints.

- Heikki




pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: "Value locking" Wiki page
Next
From: Andres Freund
Date:
Subject: Re: test_shm_mq failing on anole (was: Sending out a request for more buildfarm animals?)