| From: | "Scott Carey" <scott(at)richrelevance(dot)com> |
|---|---|
| To: | "Thomas Finneid" <tfinneid(at)student(dot)matnat(dot)uio(dot)no> |
| Cc: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: slow update of index during insert/copy |
| Date: | 2008-09-01 20:40:50 |
| Message-ID: | a1ec7d000809011340u6b4ed9b1m3cffe0ccef2c0a2e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>
>
>
> On the performance impact of using COPY instead of INSERT : out of
>> curiosity, were you comparing COPY against raw row-by-row inserts (slow) or
>> JDBC batch inserts (faster) or multi-row inserts: INSERT into X (a,b,c)
>> values (1,2,3) , (4,5,6) , (7,8,9 ) , (10,11,12) .... ?
>>
>
> I tested row by row and jdbc batch, but I dont have the measured numbers
> any more. But I suppose I could recreate the test if, need be.
>
> regards
> thomas
>
>
> Don't re-create it, I was just curious.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-09-01 20:42:07 | Re: slow update of index during insert/copy |
| Previous Message | Thomas Finneid | 2008-09-01 20:32:56 | Re: slow update of index during insert/copy |