Re: Seq scan on 10million record table.. why?

Поиск
Список
Период
Сортировка
От Vincenzo Melandri
Тема Re: Seq scan on 10million record table.. why?
Дата
Msg-id CAHSd9GdYiqCMQVuGjZDC3AUybkhtBgRAo5w_bS9=jD46pAtEHg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Seq scan on 10million record table.. why?  (Віталій Тимчишин <tivv00@gmail.com>)
Список pgsql-performance
> 1) Make all types the same
> 2) If you are using some narrow type for big_table (say, int2) to save
> space, you can force narrowing conversion, e.g. "b.key1=ds.key1::int2". Note
> that if ds.key1 has any values that don't fit into int2, you will have
> problems. And of course, use your type used instead of int2.
>
> Best regards, Vitalii Tymchyshyn
>

This fixed my problem :)
Thanks Vitalii!

For the other suggestions made from Gabriele, unfortunately I can't
make an accurate data-partitioning 'cause (obviously) it will be quite
a big work and the customer finished the budget for this year, so
unless I choose to work for free... ;)


--
Vincenzo.


В списке pgsql-performance по дате отправления:

Предыдущее
От: "Albe Laurenz"
Дата:
Сообщение: Re: Slow query, where am I going wrong?
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: High %SYS CPU usage