Re: gistchoose vs. bloat

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: gistchoose vs. bloat
Date: 2012-09-11 06:43:20
Message-ID: CAPpHfdsBQ8O3pv5cvWFj8U5MEzF1xCdyRFgpY_VXgSGQOsfRww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 11, 2012 at 10:35 AM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:

> On Tue, 2012-09-04 at 19:21 +0400, Alexander Korotkov wrote:
>
> > New version of patch is attached. Parameter "randomization" was
> > introduced. It controls whether to randomize choose. Choose algorithm
> > was rewritten.
> >
> Do you expect it to be bad in any reasonable situations? I'm inclined to
> just make it always randomize if it's better. I think it would be hard
> for a user to guess when it's better and when not.
>

Randomization should increase IO when index doesn't entirely fit to cache.
Without randomization only fraction of the tree would be used for actual
insertions. While with randomization whole tree would be potentially used
for insertions.

> Maybe it's useful to turn randomization off for testing purposes, e.g.
> to ensure determinism?
>

Yes, that's another good point. For example, randomization impede
reproducing of bugs.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2012-09-11 07:13:13 Re: Question about SSI, subxacts, and aborted read-only xacts
Previous Message Jeff Davis 2012-09-11 06:35:26 Re: gistchoose vs. bloat