Bad Index Choices with user defined data type

From: "Adam Palmblad" <adam(at)aers(dot)ca>
To: "Postgres Performance" <pgsql-performance(at)postgresql(dot)org>
Subject: Bad Index Choices with user defined data type
Date: 2005-01-03 21:44:27
Message-ID: 001d01c4f1dd$7eb98390$97019696@AERS04
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I've got a table using a data type that I have created as the type for its primary key. I (hope) I have the type set up properly - it seems okay, and does not have any problem creating a b-tree index for the type. The problem I am having is that the index seems to never be chosen for use. I can force the use of the index by setting enable_seqscan to off. The table has about 1.2 million rows. I have also analyzed the table - and immediately afterwards there is no affect on the index's behaviour.

Any thoughts?

-Adam

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Pallav Kalva 2005-01-03 22:19:15 Very Bad Performance.
Previous Message Merlin Moncure 2005-01-03 21:11:44 Re: sudden drop in statement turnaround latency -- yay!.