From: | adrobj <adrobj(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Clustered/covering indexes (or lack thereof :-) |
Date: | 2007-11-15 19:46:16 |
Message-ID: | 13780229.post@talk.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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-tf4816700.html#a13780229
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Manes | 2007-11-15 19:53:47 | ERROR: there is no parameter $1 |
Previous Message | Richard Huxton | 2007-11-15 19:28:17 | Re: Variable LIMIT and OFFSET in SELECTs |