|
|||||||||||
|
[GENERAL] Clustered/covering indexes (or lack thereof :-)
From: adrobj <adrobj(at)yahoo.com>
Date: Thu Nov 15 2007 - 14:46:16 EST 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
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. ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanlyReceived on Sat Nov 17 20:52:20 2007 This archive was generated by hypermail 2.1.8 : Mon Jun 16 2008 - 20:07:59 EDT |
||||||||||
|
|||||||||||