From: adrobj <adrobj@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: Clustered/covering indexes (or lack thereof :-)
Date: Sun, 11 Nov 2007 22:59:05 -0800 (PST)
Message-ID: <13700848.post@talk.nabble.com> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: adrobj@yahoo.com
Subject: Re: Clustered/covering indexes (or lack thereof :-)
In-Reply-To: <13700848.post@talk.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox