Marc Cousin wrote:
For PostgreSQL, there are at least 2 solutions :
- Put the textvector into the page table
- Do the same as for mysql : create a searchindex table (even if the myisam
justification for this table doesn't hold for mysql)
Plus the temporary fix I was talking about in my mail : put an empty textvector for all versions of a document except its last one, by changing the trigger a bit. That divided the size of my fulltext index by 30 and made the text search fast again.
What would be the preferred way to solve this problem ?
Probably to create a new table. The less you differ from the mysql setup, the better.