5 ms·
This is likely a query issue; I've had many queries go wild & OOM, once fixed they work as you'd expect. There's also a config setting you can use to limit in s
by raccer 9y ago
This is likely a query issue; I've had many queries go wild & OOM, once fixed they work as you'd expect. There's also a config setting you can use to limit in seconds the amount of time a query can run before it's killed, very useful if you plan on running hand built queries on anything production (which you shouldn't be anyways ;-))
- jexp 9y agoCan you share more info about the queries that "went wild" on GitHub, so that we can reproduce? Thx