Bad Index Choices with user defined data type

Поиск
Список
Период
Сортировка
От Adam Palmblad
Тема Bad Index Choices with user defined data type
Дата
Msg-id 001d01c4f1dd$7eb98390$97019696@AERS04
обсуждение исходный текст
Ответы Re: Bad Index Choices with user defined data type  (Michael Fuhr <mike@fuhr.org>)
Список 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 по дате отправления:

Предыдущее
От: "Merlin Moncure"
Дата:
Сообщение: Re: sudden drop in statement turnaround latency -- yay!.
Следующее
От: Pallav Kalva
Дата:
Сообщение: Very Bad Performance.