Bad Index Choices with user defined data type - Mailing list pgsql-performance

From Adam Palmblad
Subject Bad Index Choices with user defined data type
Date
Msg-id 001d01c4f1dd$7eb98390$97019696@AERS04
Whole thread Raw
Responses Re: Bad Index Choices with user defined data type
List 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

pgsql-performance by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: sudden drop in statement turnaround latency -- yay!.
Next
From: Pallav Kalva
Date:
Subject: Very Bad Performance.