On Wed, Jun 10, 2015 at 6:01 PM, deavid <deavidsed...@gmail.com> wrote: > By now, my results were a bit disappointing: (comparing gin_btree against > regular btree for a column with very low cardinality) > - create index and updates: about 10-20% faster (i had a primary key, so > btree unique checks may be here blurring the results)
That could be the effect of GIN's buffering (lets call it LSM? it's similar) So that with pure btrees could get a similar speedup. On Wed, Jun 10, 2015 at 6:01 PM, deavid <deavidsed...@gmail.com> wrote: > What i've found is, I was wrong on fillfactor. (Maybe something has changed > here since postgresql 8.1). I believed a fillfactor lower than 80 will do > more harm than good. At least that was the case 5 years ago. Now I could get > a noticeable speedup with fillfactor=50 in the case of updating the whole > table. 8.1 didn't have HOT. I'd bet it's that. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
