| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: "Value locking" Wiki page |
| Date: | 2014-10-01 10:50:02 |
| Message-ID: | CA+U5nMKV0zSb1CmJ67fPkoqJDUSTSQgO5vb91BbA5WbW8f4nvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1 October 2014 10:44, Heikki Linnakangas <hlinnakangas(at)vmware(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-10-01 10:58:04 | Re: "Value locking" Wiki page |
| Previous Message | Andres Freund | 2014-10-01 10:24:42 | Re: libpq-dev: pg_config_manual.h redefines CACHE_LINE_SIZE |