Re: Extreme bloating of intarray GiST indexes

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extreme bloating of intarray GiST indexes
Date: 2011-05-04 08:24:21
Message-ID: BANLkTi=TfiuwVnXiEvGiXMbpdc6brt1uPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I have another hypothesis about index bloat cause. AFAIK, vaccum procedure
on GiST don't have any storage utilization guarantee. For example, if only
one live item is in some page, then only one item will be left in this page.
I.e. there is no index reroganization during vacuum. If there wouldn't be
many inserts into such pages in future then they will be stay bloat.

----
With best regards,
Alexander Korotkov.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hitoshi Harada 2011-05-04 10:02:07 Pull up aggregate subquery
Previous Message Tomasz Chmielewski 2011-05-04 06:21:23 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?