Clustered/covering indexes (or lack thereof :-)

Поиск
Список
Период
Сортировка
От adrobj
Тема Clustered/covering indexes (or lack thereof :-)
Дата
Msg-id 13700848.post@talk.nabble.com
обсуждение исходный текст
Ответы Re: Clustered/covering indexes (or lack thereof :-)  (Heikki Linnakangas <heikki@enterprisedb.com>)
Re: Clustered/covering indexes (or lack thereof :-)  (Jeff Davis <pgsql@j-davis.com>)
Список pgsql-performance
This is probably a FAQ, but I can't find a good answer...

So - are there common techniques to compensate for the lack of
clustered/covering indexes in PostgreSQL? To be more specific - here is my
table (simplified):

topic_id int
post_id int
post_text varchar(1024)

The most used query is: SELECT post_id, post_text FROM Posts WHERE
topic_id=XXX. Normally I would have created a clustered index on topic_id,
and the whole query would take ~1 disk seek.

What would be the common way to handle this in PostgreSQL, provided that I
can't afford 1 disk seek per record returned?

--
View this message in context:
http://www.nabble.com/Clustered-covering-indexes-%28or-lack-thereof-%3A-%29-tf4789321.html#a13700848
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.


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

Предыдущее
От: "Jonah H. Harris"
Дата:
Сообщение: Re: PostgreSQL vs MySQL, and FreeBSD
Следующее
От: Ivan Voras
Дата:
Сообщение: Re: PostgreSQL vs MySQL, and FreeBSD