Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dOPWF-0006gk-Ro for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Jun 2017 14:25:07 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dOPWF-0005Js-Av for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Jun 2017 14:25:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dOPWD-0005I1-Rk for pgsql-hackers@postgresql.org; Fri, 23 Jun 2017 14:25:05 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dOPWA-00020S-U8 for pgsql-hackers@postgresql.org; Fri, 23 Jun 2017 14:25:05 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v5NEOx7e008787; Fri, 23 Jun 2017 10:24:59 -0400 From: Tom Lane To: Tomas Vondra cc: Teodor Sigaev , Michael Paquier , Robert Haas , Haribabu Kommi , Alvaro Herrera , Pg Hackers Subject: Re: Pluggable storage In-reply-to: <9b5728fc-c266-5f71-9a69-7668ad231e05@2ndquadrant.com> References: <20160824182201.GA232997@alvherre.pgsql> <20161013202642.ksiuyx72gu6wgupf@alvherre.pgsql> <8b2510f0-ab89-dbf1-5b1c-5d686a5e33b8@sigaev.ru> <9b5728fc-c266-5f71-9a69-7668ad231e05@2ndquadrant.com> Comments: In-reply-to Tomas Vondra message dated "Fri, 23 Jun 2017 16:07:44 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8785.1498227899.1@sss.pgh.pa.us> Date: Fri, 23 Jun 2017 10:24:59 -0400 Message-ID: <8786.1498227899@sss.pgh.pa.us> 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 Tomas Vondra writes: > It would be really great if you could explain why BitmapScans are > dubious, instead of just labeling them as dubious. (I guess you mean > Bitmap Heap Scans, right?) The two things I'm aware of are (a) the assumption you noted, that fetching tuples in TID sort order is a reasonably efficient thing, and (b) the "offset" part of a TID can't exceed MaxHeapTuplesPerPage --- see data structure in tidbitmap.c. The latter issue means that you don't really have a full six bytes to play with in a TID, only about five. I don't think (b) would be terribly hard to fix if we had a motivation to, but I wonder whether there aren't other places that also know this about TIDs. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers