Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDIdS-0003zl-Ho for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Feb 2014 19:04:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WDIdS-0002jA-0O for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Feb 2014 19:04:46 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDIdP-0002gx-Sv for pgsql-hackers@postgresql.org; Tue, 11 Feb 2014 19:04:44 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDIdN-0002cv-Cg for pgsql-hackers@postgresql.org; Tue, 11 Feb 2014 19:04:43 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1WDIdH-000435-DL; Tue, 11 Feb 2014 14:04:35 -0500 Date: Tue, 11 Feb 2014 14:04:35 -0500 From: Bruce Momjian To: Tom Lane Cc: Andres Freund , Robert Haas , Jim Nasby , Alvaro Herrera , Peter Geoghegan , Andrew Dunstan , PostgreSQL-development Subject: Re: [PERFORM] encouraging index-only scans Message-ID: <20140211190435.GH2289@momjian.us> References: <20140201032207.GD31141@momjian.us> <20140211155607.GB2289@momjian.us> <20140211171213.GE2289@momjian.us> <20140211175410.GF31598@awork2.anarazel.de> <20140211182319.GF2289@momjian.us> <20140211183103.GJ15246@awork2.anarazel.de> <20140211184146.GG2289@momjian.us> <25945.1392144888@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25945.1392144888@sss.pgh.pa.us> 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 01:54:48PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Tue, Feb 11, 2014 at 07:31:03PM +0100, Andres Freund wrote: > >> I am not saying it shouldn't be improved, I just don't see the point of > >> bringing it up while everyone is busy with the last CF and claiming it > >> is unusable and that stating that it is surprisising that nobody really > >> cares. > > > Well, I brought it up in September too. My point was not that it is a > > new issue but that it has been such an ignored issue for two years. I > > am not asking for a fix, but right now we don't even have a plan on how > > to improve this. > > Indeed, and considering that we're all busy with the CF, I think it's > quite unreasonable of you to expect that we'll drop everything else > to think about this problem right now. The reason it's like it is > is that it's not easy to see how to make it better; so even if we did > drop everything else, it's not clear to me that any plan would emerge > anytime soon. Well, documenting the VACUUM requirement and adding it to the TODO list are things we should consider for 9.4. If you think doing that after the commit-fest is best, I can do that. -- 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