On 14/04/16 18:34, Kevin Burke wrote:
Unfortunately *I'm still seeing a very slow query which is affecting
our tests. *It's happening with roughly the same frequency as the
previous error.
*
*
The query log is here:
https://gist.github.com/kevinburkeshyp/f1a4f73f8933e027aebbc53283acced2**
*
On 14/04/16 18:34, Kevin Burke wrote:
Unfortunately *I'm still seeing a very slow query which is affecting
our tests. *It's happening with roughly the same frequency as the
previous error.
*
*
The query log is here:
https://gist.github.com/kevinburkeshyp/f1a4f73f8933e027aebbc53283acced2**
*
Hi Alexey,
Thank you for your suggestion. We had to rewrite our constraints to be
DEFERRABLE INITIALLY IMMEDIATE, but after we did that we saw a nice speedup
in our clear-all-tables query.
Unfortunately *I'm still seeing a very slow query which is affecting our
tests. *It's happening with roughly
Hello Kevin,
On 06/04/16 23:22, Kevin Burke wrote:
/Why mess around with DISABLE/ENABLE TRIGGER instead of TRUNCATE?/ We
observed that TRUNCATE took about 200ms, but this method takes about
13ms. Over a our test suite TRUNCATE is going to more or less double
the length of the suite.
We could
