Skip site navigation (1) Skip section navigation (2)

Re: Fix pgstatindex using for large indexes

From: Tatsuhito Kasahara <kasahara(dot)tatsuhito(at)oss(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org, "kasahara(OSSC)" <kasahara(dot)tatsuhito(at)oss(dot)ntt(dot)co(dot)jp>
Subject: Re: Fix pgstatindex using for large indexes
Date: 2008-02-24 11:21:28
Message-ID: 47C15338.1080807@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-patches
Hi.

Tom Lane wrote:
>> I think that max_avail and free_space should be uint64.
> Most places where we've dealt with this before, we use double, which is
> guaranteed to be available whereas uint64 is not ...
Oh I see.

I fix the patch.
# I changed "max_avail" and "free_space" to double.

Best regards.

-- 
NTT OSS Center
Tatsuhito Kasahara

kasahara.tatsuhito _at_ oss.ntt.co.jp



Attachment: pgstatindex.patch
Description: text/plain (3.2 KB)

In response to

Responses

pgsql-patches by date

Next:From: Tatsuhito KasaharaDate: 2008-02-24 11:53:14
Subject: Re: Fix pgstatindex using for large indexes
Previous:From: Luke LonerganDate: 2008-02-24 01:46:40
Subject: Re: CopyReadLineText optimization

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group