Re: Bug in new buffering GiST build code - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Bug in new buffering GiST build code
Date
Msg-id CAPpHfdu4gmz9rRUaOzE5JDemHL6jr3pKgzf=qgSH9c2V0WTSng@mail.gmail.com
Whole thread Raw
In response to Re: Bug in new buffering GiST build code  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Bug in new buffering GiST build code
List pgsql-hackers
On Mon, May 28, 2012 at 1:46 AM, Alexander Korotkov <aekorotkov@gmail.com> wrote:
On Sat, May 26, 2012 at 12:33 AM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
Alexander, do you still have the test environments and data lying around that you used for GiST buffering testing last summer? Could you rerun some of those tests with this patch?

I think I can restore test environment and data. Will rerun tests soon.

I rerun some of tests. There are index build times in seconds for old way of parent refind and new way of it.

                  old      new
usnoa2           2385     2452
usnoa2_shuffled  8131     8055
uniform          8327     8359

I thinks difference can be described by round error.
Indexes seem to be exactly same. It's predictable because changing algorithm of parent refind shouldn't change the result.

------
With best regards,
Alexander Korotkov.

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: No, pg_size_pretty(numeric) was not such a hot idea
Next
From: Tom Lane
Date:
Subject: Re: No, pg_size_pretty(numeric) was not such a hot idea