From: Scott Carey <scott@richrelevance.com>
To: Thomas Finneid <tfinneid@student.matnat.uio.no>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Craig Ringer <craig@postnewspapers.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: slow update of index during insert/copy
Date: Mon, 1 Sep 2008 13:40:50 -0700
Message-ID: <a1ec7d000809011340u6b4ed9b1m3cffe0ccef2c0a2e@mail.gmail.com> (raw)
In-Reply-To: <48BC5178.60906@ifi.uio.no>
References: <48BA9D65.2020001@ifi.uio.no>
<48BB4A2D.9080404@postnewspapers.com.au>
<48BBD22E.4090308@ifi.uio.no>
<dcc563d10809011051s558f8a7bp5beb0dbe181721e4@mail.gmail.com>
<a1ec7d000809011146x456b942eof33627c63f8a021a@mail.gmail.com>
<48BC5178.60906@ifi.uio.no>
>
>
>
> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott@richrelevance.com, tfinneid@student.matnat.uio.no, scott.marlowe@gmail.com, craig@postnewspapers.com.au
Subject: Re: slow update of index during insert/copy
In-Reply-To: <a1ec7d000809011340u6b4ed9b1m3cffe0ccef2c0a2e@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox