@@ -13,11 +13,10 @@ Ofcourse we can write this as:
1313
1414But this does not use any indices, and therefore, if your database
1515gets very large, it will not have very high performance (the above query
16- requires at least one sequential scan, it probably takes 2 due to the
17- self-join).
16+ requires a sequential scan of the table).
1817
1918The approach used by this add-on is to define a trigger on the table and
20- columns you want to dothis queries on. On every insertin the table, it
19+ columns you want to dothese queries on. On every insertto the table, it
2120takes the value in the specified columns, breaks the text in these columns
2221up into pieces, and stores all sub-strings into another table, together
2322with a reference to the row in the original table that contained this
@@ -27,7 +26,7 @@ By now creating an index over the 'fti-table', we can search for
2726substrings that occur in the original table. By making a join between
2827the fti-table and the orig-table, we can get the actual rows we want
2928(this can also be done by using subselects - but subselects are currently
30- inefficient inPostgres , and maybe there're other ways too).
29+ inefficient inPostgreSQL , and maybe there're other ways too).
3130
3231The trigger code also allows an array called StopWords, that prevents
3332certain words from being indexed.