| From: | "Steven Flatt" <steven(dot)flatt(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, "Vivek Khera" <vivek(at)khera(dot)org>, "Pgsql performance" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: When/if to Reindex |
| Date: | 2007-08-09 13:51:42 |
| Message-ID: | 357fa7590708090651p71b9bc47n66739f8dbbb4ff57@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 8/8/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I'd make the same remark about Steven's case: if possible, don't create
> the indexes at all until you've loaded the table fully.
We considered this, however in some of our 12-hour partitions, there are
upwards of 50 or 60 million rows near the end of the 12 hours so read
performance gets bad on the current partition very quickly if there are no
indexes.
It makes more sense for us to have ~1 hour's worth of reindexing afterwards
during which read performance on that partition is "compromised".
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivek Khera | 2007-08-09 14:40:30 | Re: mid 2007 "best bang for the buck" hardware opinions |
| Previous Message | Trevor Talbot | 2007-08-09 13:41:50 | Re: Update table performance |