Search Postgresql Archives

explicit deadlock-victim-priority mechanism

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



ref =  [ E1QZDJc-0000XV-C8@xxxxxxxxxxxxxxxxxxxxxx ]

I note with interest that [deadlock_timeout] can be used as . . .
"a poor-man's deadlock priority mechanism: a transaction with a high [deadlock_timeout] is less
likely to be chosen as the victim than one with a low [deadlock_timeout]"

I for one, would definitely be interested in "a more explicit priority mechanism".

My use case is:
We have some "batch work" processes, whose "deadlock-victim-priority" I would like to set to HIGH.
(at the expense of smaller transactions who I would like to be the victim)

-dvs-




-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux