From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GiST buffering build, bug in levelStep calculation |
Date: | 2012-05-29 20:20:50 |
Message-ID: | CAPpHfds9r4VAu=4te8wCMT4_kuPxDhGfsdJ7rcHqkkrzM0wgXw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 29, 2012 at 11:42 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> While I'm looking at this, is the first test involving
> effective_cache_size bulletproof either? In particular, is
> avgIndexTuplesPerPage clamped to be strictly greater than 1?
>
It's based on collected statistics on already inserted tuple sizes. Since
tuple sizes are measured after possible toasting, I don't see the way
for avgIndexTuplesPerPage to be less than 1.
> And for that matter, is either test sane from a units standpoint?
> It seems to me that maxIndexTuplesPerPage would have units of
> 1/blocks, which is pretty dubious to be comparing to a block count
> even disregarding the power function.
>
In this test we use avgIndexTuplesPerPage as estimate for number of child
index pages of one page. I think we can assume it to have blocks unit.
------
With best regards,
Alexander Korotkov.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-05-29 20:25:02 | Re: GiST buffering build, bug in levelStep calculation |
Previous Message | Tom Lane | 2012-05-29 20:10:41 | Re: pg_upgrade libraries check |