Re: Promise index tuples for UPSERT
| От | Peter Geoghegan |
|---|---|
| Тема | Re: Promise index tuples for UPSERT |
| Дата | |
| Msg-id | CAM3SWZR=tAs-TNioasca+ipUxMjWadre7V2maebgxAM93Zzj3Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Promise index tuples for UPSERT (Heikki Linnakangas <hlinnakangas@vmware.com>) |
| Ответы |
Re: Promise index tuples for UPSERT
|
| Список | 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 по дате отправления: