Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YD7US-0007WT-PW for pgsql-general@arkaria.postgresql.org; Mon, 19 Jan 2015 08:15:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YD7US-0003Gm-4s for pgsql-general@arkaria.postgresql.org; Mon, 19 Jan 2015 08:15:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YD7UQ-0003GH-Ny for pgsql-general@postgresql.org; Mon, 19 Jan 2015 08:15:14 +0000 Received: from hogranch.com ([75.101.82.47]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YD7UJ-0002Mz-FN for pgsql-general@postgresql.org; Mon, 19 Jan 2015 08:15:13 +0000 Received: from [192.168.0.2] (porker [192.168.0.2]) by hogranch.com (8.11.6/8.11.6) with ESMTP id t0J8F0H30566 for ; Mon, 19 Jan 2015 00:15:01 -0800 Message-ID: <54BCBCFF.5040100@hogranch.com> Date: Mon, 19 Jan 2015 00:14:55 -0800 From: John R Pierce User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: pgsql-general@postgresql.org Subject: Re: Partitioning References: <54BC71EF.4050505@hogranch.com> <20150119.150952.127015115.horiguchi.kyotaro@lab.ntt.co.jp> <54BCB0E2.5020405@hogranch.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------030602090503020203040106" X-HawgScanner-Information: Please contact the ISP for more information X-HawgScanner: Found to be clean X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org This is a multi-part message in MIME format. --------------030602090503020203040106 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 1/18/2015 11:59 PM, James Sewell wrote: > > Actually this brings up another question, if I have an unique integer > index of 2.gb what percentage would I expect to read for > a value that was higher or lower than all index values? a couple 8k blocks. its a b-tree. -- john r pierce 37N 122W somewhere on the middle of the left coast --------------030602090503020203040106 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
On 1/18/2015 11:59 PM, James Sewell wrote:

Actually this brings up another question, if I have an unique integer index of 2.gb what percentage would I expect to read for a value that was higher or lower than all index values?

a couple 8k blocks.  its a b-tree.

-- 
john r pierce                                      37N 122W
somewhere on the middle of the left coast
--------------030602090503020203040106--