Am 09.05.2013 22:58, schrieb Robinson, Eric:
> Q: What conditions could cause single query to lock up a database for a while for all
A SELECT statement that takes a long time to run prevents other
sessions from updating the table in the meantime, making the
other sessions appear slow or unresponsive. While a session is
waiting to get exclusive access to the table for updates, other
sessions that issue SELECT statements will queue up behind it,
reducing concurrency even for read-only sessions.
You might try using low_priority_updates to mitigate this.
syneticon networks gmbh