On Tue, Jul 5, 2016 at 11:05 PM, Oskari Saarenmaa <os@aiven.io> wrote:
> ISTM this is caused by toast knowing nothing about speculative insertion:
> when two backends have executed a speculative heap_insert with a conflicting
> key and the latter one tries to abort after receiving specConflict there's
> nothing in tqual.c to say that the toast rows associated with speculative
> insertion should be visible to that operation.
This analysis may be relevant:
https://www.postgresql.org/message-id/CACjxUsMBEHexQehM6P7ck+7AdxReH9fP29Z3t6h4eZp_9YveXQ@mail.gmail.com
--
Peter Geoghegan
