Each connection/session establishes for itself what level of dirtiness it's willing to put up with. There's no way for a different connection to suddenly force a connection to see dirtier data (or, conversely, to be more strict)
The SELECT
s have all of the control over their own locking/blocking behaviour. And UPDATE
s always have to apply some exclusive locks to complete successfully. So if you cannot change the SELECT
s, then you can't overcome your current situation.