Postgresql ILIKE versus TSEARCH

后端 未结 3 879
天涯浪人
天涯浪人 2020-12-17 02:07

I have a query with a number of test fields something like this:

SELECT * FROM some-table
  WHERE field1 ILIKE \"%thing%\"
     OR field2 ILIKE \"%thing\"
           


        
3条回答
  •  隐瞒了意图╮
    2020-12-17 03:00

    Adding a bit to what the others have said.

    First you can't really use an index based on a value in the middle of the string. Indexes are tree searches generally, and you have no way to know if your search will be faster than just scanning the table, so PostgreSQL will default to a seq scan. Indexes will only be used if they match the first part of the string. So:

    SELECT * FROM invoice
      WHERE invoice_number like 'INV-2012-435%'
    

    may use an index but like '%44354456%' cannot.

    In general in LedgerSMB we use both, depending on what kind of search we are doing. You might see a search like:

    select * from parts
      WHERE partnumber ilike ?  || '%'
        and plainto_tsquery(get_default_language(), ?) @@ description;
    

    So these are very different. Use each one where it makes the most sense.

提交回复
热议问题