From: | Nick Raj <nickrajjain(at)gmail(dot)com> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Cube Index Size |
Date: | 2011-06-02 05:16:17 |
Message-ID: | BANLkTi=m3G2ttjP7PCRs88iuOpJ9WiUKdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2011/6/1 Alexander Korotkov <aekorotkov(at)gmail(dot)com>
> 2011/6/1 Teodor Sigaev <teodor(at)sigaev(dot)ru>
>>
>> One of idea is add sorting of Datums to be splitted by cost of insertion.
>> It's implemented in intarray/tsearch GiST indexes.
>>
>
> Yes, it's a good compromise between linear and quadratic entries
> distribution algorithms. In quadratic algorithm each time entry with maximal
> difference of inserion cost is inserted. Quadratic algorithm runs slowly
> than sorting one, but on my tests it shows slightly better results.
>
>
> Can we figure out some information about index i.e. whet is the height of
index tree, how many values are placed in one leaf node and one non leaf
level node?
Regards,
Nick
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-06-02 06:29:08 | is there any reason why don't create context info for RAISE EXCEPTION? |
Previous Message | Noah Misch | 2011-06-02 04:59:55 | Re: pg_terminate_backend and pg_cancel_backend by not administrator user |