Hackers,
Since querying pg_locks can be intrusive due to needing to lock the lock
partitions, when I'm collecting data about locks I generally put a
statement_timeout on it. However, I'm noticing that this
statement_timeout appears to be completely ignored; I've seen this query
run for up to 10
Josh Berkus j...@agliodbs.com writes:
Since querying pg_locks can be intrusive due to needing to lock the lock
partitions, when I'm collecting data about locks I generally put a
statement_timeout on it. However, I'm noticing that this
statement_timeout appears to be completely ignored; I've
On 11/18/2014 10:47 AM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Since querying pg_locks can be intrusive due to needing to lock the lock
partitions, when I'm collecting data about locks I generally put a
statement_timeout on it. However, I'm noticing that this
statement_timeout