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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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 Content-Type Size
pgstatindex.patch text/plain 3.2 KB

In response to

Responses

Browse pgsql-patches by date

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