"Janek Sendrowski" <janek12@xxxxxx> writes: > How can I use this ORDER BY using index feature presented in this implementation. > It doesn't seem to be in use, when I have a look in my query plan. > It still does an cost intensive Bitmap Heap Scan and a Bitmap Index scan. > I also can't find the "><" operator in any introduction of the tsearch2 extension. > Is it just an idea? We're not in the habit of documenting nonexistent features, if that's what you mean. However, you've not provided nearly enough information for anyone to help you; at minimum, the index definitions you have, the query you gave, the plan you got, and the exact PG version would be critical information. More information about asking answerable questions can be found here: https://wiki.postgresql.org/wiki/Slow_Query_Questions Also, I'm a bit troubled by your reference to tsearch2, because that contrib module is obsolete, and has been since well before any PG version that has a feature like what I think you're asking about. So I wonder if you are reading documentation not applicable to the version you're working with. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
