From: | "David Wilson" <david(dot)t(dot)wilson(at)gmail(dot)com> |
---|---|
To: | "Alex Vinogradovs" <AVinogradovs(at)clearpathnet(dot)com> |
Cc: | "Joshua Drake" <jd(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: non-WAL btree? |
Date: | 2008-08-01 20:18:49 |
Message-ID: | e7f9235d0808011318x77f71a37k8cb983586c65997c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Aug 1, 2008 at 4:16 PM, David Wilson <david(dot)t(dot)wilson(at)gmail(dot)com> wrote:
> On Fri, Aug 1, 2008 at 4:07 PM, Alex Vinogradovs
> <AVinogradovs(at)clearpathnet(dot)com> wrote:
>> By loading in bulks, I mean I load some 40-50 thousand
>> rows at once into a table that already has some millions.
>> Index rebuild on that table after each 50k inserts will
>> be even less efficient ;)
>
> How many indexes do you have on this...? I do this pretty regularly
> (actually, I do 4k batches with COPY, 4-10 concurrent batches every 10
> seconds, for 2-3 days at a time) and, having testing dropping indices,
> nothing to do with the index has a particularly strong performance
> impact.
Sorry, as I hit send, I realized I should clarify this: I do my bulk
loads with the indexes active; I don't rebuild them (as they're
necessary during the batch calculations). Dropping the indexes and
using test data didn't show a significant performance improvement over
leaving the indexes enabled.
--
- David T. Wilson
david(dot)t(dot)wilson(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Vinogradovs | 2008-08-01 20:32:23 | Re: non-WAL btree? |
Previous Message | Joshua Drake | 2008-08-01 20:16:26 | Re: non-WAL btree? |