| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A strange GiST error message or fillfactor of GiST build |
| Date: | 2018-09-03 18:09:33 |
| Message-ID: | 0477DB18-95C3-4262-BDC1-E7C7C176C99C@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 3 сент. 2018 г., в 20:16, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> написал(а):
>
> That's a good idea. Especially if we take into account that
> fillfactor is not a forever bad idea for GIST, it just doesn't look
> reasonable for current building algorithm. So, we can decide to
> ignore it, but if we would switch to different GiST building
> algorithm, which can pack pages tightly, we can take fillfactor into
> account again.
BTW, I think that build algorithm may be provided by opclass.
>
> I think I need to prove my position about GiST fillfactor with some
> experiments first, and then propose a patch.
FWIW fillfactor can be a cheap emulator for intrapage indexing, when you have like a lot of RAM. Though I didn't tested that.
Also I believe proper intrapage indexing is better :)
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-09-03 18:33:35 | Re: Caching query plan costs |
| Previous Message | Tom Lane | 2018-09-03 17:30:33 | Re: Caching query plan costs |