Gregory's Server@bclindner There's no limit to what you can do... Make a query that does a seqscan and then join it to another table which also requires a seqscan, and then join more and more, and then maybe re-order it too
|
Top-level
 @bclindner There's no limit to what you can do... Make a query that does a seqscan and then join it to another table which also requires a seqscan, and then join more and more, and then maybe re-order it too No comments
|
@Gargron i probably should have phrased my question differently because the SELECT stuff is already hashed out, i'm just trying to find out what makes it go slow...
i'd like to see what the app can take, because right now it's simple enough that it's going over ~1000 entries in <5ms and i gotta pump up those numbers. i need to see my own backend cry