On Wed, Aug 31, 2011 at 11:53 PM, Kevin Grittner <
kevin.gritt...@wicourts.gov> wrote:
> Viktor Bojovi* wrote:
>
> > i don't know why it doesn't use index scan.
>
> Because it thinks your query will return 81226 rows. We need more
> information to make many suggestions beyond "make sure the table
Viktor Bojovi* wrote:
> i don't know why it doesn't use index scan.
Because it thinks your query will return 81226 rows. We need more
information to make many suggestions beyond "make sure the table has
been analyzed".
http://wiki.postgresql.org/wiki/SlowQueryQuestions
Also, it's not consi
Hi,
on table entry (17M records) there is one index:
CREATE INDEX ndxlen
ON uniprot_frekvencije.entry
USING btree
(length(sequence::text));
When using ">=" in search which returns only two records, query runs much
(hundred times) slower. i don't know why it doesn't use index scan. I just
wa
