Are Spotlight monitoring sessions given a low priority to make sure they are deadlocks victim ? (4341701)

How to set all spotlight sessions to the lowest priority by default without affecting spotlight's functionality.

Are Spotlight monitoring sessions given a low priority to make sure they are designated as the deadlocks victim if they get caught in a deadlocked with another session? The only known way is setting a deadlock priority using the " SET DEADLOCK_PRIORITY" command, but the problem is that it can only work for the current session.

We set deadlock priority to -10 in scripts that have previously been involved in deadlocks. And we don't reset it at the end of those scripts so I it should stay set for the lifetime of the monitoring session.  However just to be safe we have an enhancement request which will address this issue in a future release (enhancement reference number JIRA SOSSE-2825 to have it set at the very start of the session.