Re: Promise index tuples for UPSERT - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Promise index tuples for UPSERT
Date
Msg-id CAM3SWZR=tAs-TNioasca+ipUxMjWadre7V2maebgxAM93Zzj3Q@mail.gmail.com
Whole thread Raw
In response to Re: Promise index tuples for UPSERT  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Promise index tuples for UPSERT
List pgsql-hackers
On Wed, Oct 1, 2014 at 12:54 PM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> XactLockTableWait() waits until the end of transaction, that's not you want
> here. If the backend that inserted the promise tuple decides to not proceed
> with the insertion, and removes the promise tuple, the backend waiting on it
> needs to be woken up more or less immediately, not when the transaction
> completes.

Simon has not been inconsistent here: he has said that deadlocks may
be possible. I happen to think that allowing them would be a major
mistake on our part, but that's another story.


-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Promise index tuples for UPSERT
Next
From: Stephen Frost
Date:
Subject: Re: pg_background (and more parallelism infrastructure patches)