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

From Simon Riggs
Subject Re: "Value locking" Wiki page
Date
Msg-id CA+U5nMKV0zSb1CmJ67fPkoqJDUSTSQgO5vb91BbA5WbW8f4nvQ@mail.gmail.com
Whole thread Raw
In response to Re: "Value locking" Wiki page  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: "Value locking" Wiki page
List pgsql-hackers
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.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: libpq-dev: pg_config_manual.h redefines CACHE_LINE_SIZE
Next
From: Heikki Linnakangas
Date:
Subject: Re: "Value locking" Wiki page