Re: serializable transaction: exclude constraint violation (backed byGIST index) instead of ssi conflict - Mailing list pgsql-hackers

From Peter Billen
Subject Re: serializable transaction: exclude constraint violation (backed byGIST index) instead of ssi conflict
Date
Msg-id CAMTXbE8o6-K5CB2KTeTkDx_y25dO_rCTqnAJ7KHjYTMvkVAxUQ@mail.gmail.com
Whole thread Raw
In response to Re: serializable transaction: exclude constraint violation (backed byGIST index) instead of ssi conflict  (Peter Billen <peter.billen@gmail.com>)
Responses Re: serializable transaction: exclude constraint violation (backed byGIST index) instead of ssi conflict
List pgsql-hackers
On Thu, Apr 11, 2019 at 6:12 PM Peter Billen <peter.billen@gmail.com> wrote:

I believe we are after multiple issues/improvements:

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.

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Reducing the runtime of the core regression tests
Next
From: Andres Freund
Date:
Subject: Re: setLastTid() and currtid()