Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDHzX-0002hI-Rt for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Feb 2014 18:23:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WDHzX-0007xS-8K for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Feb 2014 18:23:31 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDHzV-0007xJ-TH for pgsql-hackers@postgresql.org; Tue, 11 Feb 2014 18:23:30 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDHzS-0001tH-F1 for pgsql-hackers@postgresql.org; Tue, 11 Feb 2014 18:23:29 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1WDHzL-0002oU-Go; Tue, 11 Feb 2014 13:23:19 -0500 Date: Tue, 11 Feb 2014 13:23:19 -0500 From: Bruce Momjian To: Andres Freund Cc: Robert Haas , Jim Nasby , Alvaro Herrera , Peter Geoghegan , Tom Lane , Andrew Dunstan , PostgreSQL-development Subject: Re: [PERFORM] encouraging index-only scans Message-ID: <20140211182319.GF2289@momjian.us> References: <20130907053449.GE626072@alap2.anarazel.de> <5238854F.5040708@nasby.net> <20130917231050.GD29545@awork2.anarazel.de> <20140201032207.GD31141@momjian.us> <20140211155607.GB2289@momjian.us> <20140211171213.GE2289@momjian.us> <20140211175410.GF31598@awork2.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140211175410.GF31598@awork2.anarazel.de> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On Tue, Feb 11, 2014 at 06:54:10PM +0100, Andres Freund wrote: > On 2014-02-11 12:12:13 -0500, Bruce Momjian wrote: > > Yes, that pretty much sums it up. We introduced index-only scans in 9.2 > > (2012) but they still seem to be not usable for insert-only workloads > > two years later. Based on current progress, it doesn't look like this > > will be corrected until 9.5 (2015). I am kind of confused why this has > > not generated more urgency. > > I think this largely FUD. They are hugely beneficial in some scenarios > and less so in others. Just like lots of other features we have. I don't understand. Index-only scans are known to have benefits --- if an insert-only workload can't use that, why is that acceptable? What is fear-uncertainty-and-doubt about that? Please explain. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers