Re: Refactoring speculative insertion with unique indexes a little - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Refactoring speculative insertion with unique indexes a little
Date
Msg-id 20151003133810.GD3323@alap3.anarazel.de
Whole thread Raw
In response to Refactoring speculative insertion with unique indexes a little  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Refactoring speculative insertion with unique indexes a little  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
Hi,

On 2015-06-10 16:19:27 -0700, Peter Geoghegan wrote:
> Currently, speculative insertion (the INSERT ... ON CONFLICT DO UPDATE
> executor/storage infrastructure) uses checkUnique ==
> UNIQUE_CHECK_PARTIAL for unique indexes, which is a constant
> originally only used by deferred unique constraints. It occurred to me
> that this has a number of disadvantages:
> ...
> Attached patch updates speculative insertion along these lines.
> ...
> The patch also updates the AM interface documentation (the part
> covering unique indexes). It seems quite natural to me to document the
> theory of operation for speculative insertion there.

I'm not arguing against any of this - but I don't think this needs to be
on the 9.5 open items list. I plan to remove from there.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Why can't we used CAPITAL LETTERS into replication slot_name?
Next
From: Michael Paquier
Date:
Subject: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.