News for hackers. Stuff that matters.
Re:PostgreSQL 9.6 Released by kuschku on Thursday September 29, 2016 @04:03PM (#12608334)
> usually big enough to be stored in a TOAST table

Ah, luckily, in my case, that can’t happen – each row’s message contains one IRC message, so at most 512 bytes. That also automatically ensures we’ll never run into TOAST issues.

Re:PostgreSQL 9.6 Released by ngrilly on Thursday September 29, 2016 @06:23PM (#12609304)
Now I understand why you didn't suffer from the slow ranking issue. In my test case, text is longer and triggers the TOAST management code.
Re:PostgreSQL 9.6 Released by kuschku on Thursday September 29, 2016 @06:25PM (#12609317)
Yeah, if your vectors are in TOAST, you really have a huge issue with ranking. There’s no simple way to get around that, except with customized solutions like Lucene/Solr/ES