| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Ants Aasma <ants(at)cybertec(dot)at>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: very very slow inserts into very large table |
| Date: | 2012-07-17 16:55:49 |
| Message-ID: | CAGTBQpZ6+VF5WKz8UQaKdWhznV3Ry=HuQnvRRhOk-nGV_t1gkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jul 17, 2012 at 1:24 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> Also, while indexes are not formally kept in logical order, but they
> do tend to be biased in that direction in most cases. I've found that
> even if you are only inserting one row for every 4 or 5 leaf pages,
> you still get substantial improvement by doing so in sorted order.
Yep, I do the same. Whenever I have to perform massive updates, I sort them.
Although "massive" for me is nowhere near what "massive" for the OP is.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Blackwell | 2012-07-17 17:37:43 | Re: Slow application response on lightly loaded server? |
| Previous Message | Scott Marlowe | 2012-07-17 16:35:03 | Re: Slow application response on lightly loaded server? |