News for hackers. Stuff that matters.
Re:PostgreSQL 9.6 Released by brightball on Thursday September 29, 2016 @03:20PM (#12608028)
Ordering can get expensive no matter what just base on how many things you're actually sorting. Ideally, if you can find a way to limit the size of the data set before the ranking sort you'll see a big improvement.
Re:PostgreSQL 9.6 Released by ngrilly on Thursday September 29, 2016 @03:38PM (#12608170)
Currently, the only way to make ranking tolerable is to limit the size of the data set before the ranking sort. This is what I did in my tests.

But it looks like it could be possible to massively improve ranking performance by storing all necessary information directly in the GIN index, as proposed here:

https://wiki.postgresql.org/images/2/25/Full-text_search_in_...