Hello Tom,
Thank you for the clarification!
Regards,
Thomas
Le lun. 9 avr. 2018 à 17:04, Tom Lane a écrit :
> Christophe Pettus writes:
> >> On Apr 9, 2018, at 07:33, Thomas Poty wrote:
> >> ok, and long answer ? is it random?
>
> > It's not literally random, but from the application point
Christophe Pettus writes:
>> On Apr 9, 2018, at 07:33, Thomas Poty wrote:
>> ok, and long answer ? is it random?
> It's not literally random, but from the application point of view, it's not
> predictable. For example, it's not always the one that opened first, or any
> other consistent meas
> On Apr 9, 2018, at 07:33, Thomas Poty wrote:
>
> ok, and long answer ? is it random?
It's not literally random, but from the application point of view, it's not
predictable. For example, it's not always the one that opened first, or any
other consistent measure.
--
-- Christophe Pettus
Hello Stephen,
> The short answer is "it's whichever one detected the deadlock." The
> deadlock timeout fires after a lock has been held that long and if a
> deadlock is detected then the process detecting it will be canceled.
ok, and long answer ? is it random?
> I'd strongly recommend revie
Greetings,
* Thomas Poty (thomas.p...@gmail.com) wrote:
> My question is : In case of a deadlock between 2 transaction, how to know
> which transaction will be canceled? Is it predictable?
The short answer is "it's whichever one detected the deadlock." The
deadlock timeout fires after a lock ha
Good afternoon,
My question is : In case of a deadlock between 2 transaction, how to know
which transaction will be canceled? Is it predictable?
I have tried to look into sources but i have found nothing. ( probably, i
am the problem)
Regards,
Thomas
