Re: serializable transaction: exclude constraint violation (backed by GIST index) instead of ssi conflict

From: Peter Billen <peter(dot)billen(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Shubham Barai <shubhambaraiss(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>
Subject: Re: serializable transaction: exclude constraint violation (backed by GIST index) instead of ssi conflict
Date: 2019-04-11 18:01:11
Message-ID: CAMTXbE8o6-K5CB2KTeTkDx_y25dO_rCTqnAJ7KHjYTMvkVAxUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 11, 2019 at 6:12 PM Peter Billen <peter(dot)billen(at)gmail(dot)com> wrote:

>
> I believe we are after multiple issues/improvements:
>
> 1. Could we extend
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=fcff8a575198478023ada8a48e13b50f70054766
> by adding support for exclude constraints?
> 2. Fully support gist & constraints in serializable transactions. I did
> not yet test a unique constraint backed by a gist constraint, which is also
> interesting to test I assume. This test would tell us if there currently is
> a status quo between btree and gist indexes.
>

Regarding the remark in (2), I forgot that a unique constraint cannot be
backed by a gist index, so forget the test I mentioned.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-04-11 18:05:25 Re: setLastTid() and currtid()
Previous Message Alvaro Herrera 2019-04-11 18:00:30 Re: Reducing the runtime of the core regression tests