| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extreme bloating of intarray GiST indexes |
| Date: | 2011-05-04 02:28:05 |
| Message-ID: | 29952.1304476085@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> So, some data:
> corp=# select * from public.pgstattuple('idx__listings_features');
> -[ RECORD 1 ]------+---------
> table_len | 54190080
> tuple_count | 7786
> tuple_len | 2117792
> tuple_percent | 3.91
> dead_tuple_count | 0
> dead_tuple_len | 0
> dead_tuple_percent | 0
> free_space | 49297536
> free_percent | 90.97
> ^^^^^^^^^
> Well, that explains the bloating. Why all that free space, though?
> Maybe autovac isn't running?
No, because you have under 10% dead tuples in the main table.
I think this is sufficient proof of the crummy-page-splits theory.
Can you provide the data in the column that's indexed?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-05-04 02:36:13 | Re: Predicate locking |
| Previous Message | Kevin Grittner | 2011-05-04 02:07:57 | Re: Predicate locking |