Re: Table with million rows - and PostgreSQL 9.1 is not using the index

On Wednesday, December 05, 2012 02:44:39 AM Edson Richter wrote:
> Sort  (cost=11938.72..11938.74 rows=91 width=93)
>    Sort Key: t0.nome
>    ->  Nested Loop  (cost=0.00..11938.42 rows=91 width=93)
>          ->  Nested Loop  (cost=0.00..11935.19 rows=91 width=85)
>                ->  Seq Scan on logradouro t2  (cost=0.00..11634.42
> rows=91 width=81)
>                      Filter: ((cep)::text ~~ '81630160%'::text)

According to that the logradouro table only has 91 rows, which is why it seq-
scanned it. Has it been analyzed?

Also, partial text matches require a special index declaration, as I recall.
Maybe post a \d of each table to help troubleshoot this.