Johann du Toit

Anyone? Just started happening to us too. Edit: for anyone running into this as well, I upgraded the container and changed the domain name a bit - removed a domain...

yet another +1

I know this is old, but we had the same issue... I made a change to at least do the expanding asynchronously and give the browser time to redraw the...

I've got some SQL optimization experience. I don't have an instance with real data and real load to run these on. Any chance you can run this with: `EXPLAIN (ANALYZE,...

Thanks @Nutomic - I'll have a look tonight after work. And agree on the sentiment that `IN` queries are slow when there are lots of IDs to check.

@Nutomic - I had a quick look (I'm only looking at Query 1). Generally it's using indexes everywhere, so let's not try to over-optimize, but the final top level NESTED...

So while waiting for the results of running without sorting, I've looked more into the hot_rank() function. I found @dessalines 's [DBA Stack Exchange Post](https://dba.stackexchange.com/questions/284052/how-to-create-an-index-based-on-a-time-based-function-in-postgres) talking about it. In the...

Also looked at Query 4. This one seems more straight-forward. Everything is fast and indexed, except for grabbing the correct row(s) from the post table. This WHERE clause is causing...

@Nutomic - I was pretty confident it was the hot_rank. If it was only a query fix, I might've had some time to do a PR, but as per one...

> Whoa... I didn't know why I didn't think of that. And then just run a periodic job to update that hot_rank column, rather than reindex the table? @dessalines -...