Tag Info

New answers tagged

0

How would you write the FULL OUTER JOIN if it were available. (I don't see the need for it in your case.) p.title like '%%' is a costly no-op. Remove it from the WHERE clause. (I assume you are building the WHERE on the fly? If so, make your code a little smarter.) pl.stageNumber = 60.60 OR pl.stageNumber < 60.60 --> pl.stageNumber <= 60.60 ...


1

In real world environments the situations where a keyword is encountered and then removed and will never be encountered again is quite low. The process for updating a record in the full text index process probably removes all previous references to the record then updates all new references. As such when the references to a keyword are removed it does not ...


2

Your problem is probably due to the difference from 9.3.4 to 9.3.5, see the manual for that, where it states: E.2.1. Migration to Version 9.3.5 A dump/restore is not required for those running 9.3.X. However, this release corrects a logic error in pg_upgrade, as well as an index corruption problem in some GiST indexes. See the first two ...


5

First, ignore the key_len of explain, that value only has a meaning in the context of a BTREE index, so it will always be 0 for a FULLTEXT scan, regardless of the actual size of the index/column. Second, by default, the FULLTEXT index is used in "natural language mode", which, as it is documented, will ignore results that happen in 50% or more of the rows ...


0

You should really consider upgrading to a more recent version, especially if you want to utilize some of the best parts of Full Text Search. To your question, the short answer is yes. From the documentation for 2005, you have two main features to customize in a thesaurus, Expansion Sets and Replacement Sets: An expansion set contains a group of ...



Top 50 recent answers are included