Re: Why is indexonlyscan so darned slow?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ants Aasma <ants(at)cybertec(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is indexonlyscan so darned slow?
Date: 2012-05-21 20:42:26
Message-ID: 4FBAA8B2.7010601@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Earlier you said that this should be an ideal setup for IOS. But it
> isn't really--the ideal set up is one in which the alternative to an
> IOS is a regular index scan which makes many uncached scattered reads
> into the heap. I don't think that that situation can't really be
> engineered with a where-less query.

Can you give me some suggested comparisons which *would* be ideal, then?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2012-05-21 20:56:05 Re: Bug in new buffering GiST build code
Previous Message Simon Riggs 2012-05-21 20:37:06 Re: Why is indexonlyscan so darned slow?