Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bwuJI-00035D-87 for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Oct 2016 17:05:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bwuJH-0004Hj-ML for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Oct 2016 17:05:47 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bwuHt-0002hH-Gl for pgsql-hackers@postgresql.org; Wed, 19 Oct 2016 17:04:21 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bwuHp-00049F-Va for pgsql-hackers@postgresql.org; Wed, 19 Oct 2016 17:04:20 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1bwuHo-0006PI-5r; Wed, 19 Oct 2016 13:04:16 -0400 Date: Wed, 19 Oct 2016 13:04:16 -0400 From: Bruce Momjian To: Simon Riggs Cc: Pavan Deolasee , Alexander Korotkov , Robert Haas , Alvaro Herrera , Pg Hackers Subject: Re: Indirect indexes Message-ID: <20161019170416.GR5087@momjian.us> References: <20161018182843.xczrxsa2yd47pnru@alvherre.pgsql> <20161019164043.GN5087@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -2.2 (--) 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 Wed, Oct 19, 2016 at 06:58:05PM +0200, Simon Riggs wrote: > >> I agree. Also, I think the recheck mechanism will have to be something like > >> what I wrote for WARM i.e. only checking for index quals won't be enough and we > >> would actually need to verify that the heap tuple satisfies the key in the > >> indirect index. > > > > I personally would like to see how far we get with WARM before adding > > this feature that requires a DBA to evaluate and enable it. > > Assuming WARM is accepted, that *might* be fine. First, I love WARM because everyone gets the benefits by default. For example, a feature that improves performance by 10% but is only used by 1% of users has a usefulness of 0.1% --- at least that is how I think of it. > What we should ask is what is the difference between indirect indexes > and WARM and to what extent they overlap. > > My current understanding is that WARM won't help you if you update > parts of a JSON document and/or use GIN indexes, but is effective > without needing to add a new index type and will be faster for > retrieval than indirect indexes. > > So everybody please chirp in with benefits or comparisons. I am not sure we have even explored all the limits of WARM with btree indexes --- I haven't heard anyone talk about non-btree indexes yet. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers