From: Thomas Finneid <tfinneid@student.matnat.uio.no>
To: Scott Carey <scott@richrelevance.com>
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, 01 Sep 2008 22:32:56 +0200
Message-ID: <48BC5178.60906@ifi.uio.no> (raw)
In-Reply-To: <a1ec7d000809011146x456b942eof33627c63f8a021a@mail.gmail.com>
References: <48BA9D65.2020001@ifi.uio.no>
<48BB4A2D.9080404@postnewspapers.com.au>
<48BBD22E.4090308@ifi.uio.no>
<dcc563d10809011051s558f8a7bp5beb0dbe181721e4@mail.gmail.com>
<a1ec7d000809011146x456b942eof33627c63f8a021a@mail.gmail.com>
Scott Carey wrote:
> For a development box, just enable write-back caching regardless of the
> battery back up situation. As long as its not your only copy of
Will have a look at it, the data is not important and can be reproduced
any time on any machine. The controller I have is a Areca ARC-1220
Serial ATA 8 port RAID Controller - PCI-E, SATA II, so I dont know
exactly what it supports of caching.
> On JDBC and COPY:
> Thanks for the info on the patch to support it -- however the versions
> posted there are rather old, and the 8.3 version is not even the same as
> the 8 month old current release -- its 3 releases prior and 8 months
> older than that. There are quite a few bugfixes between 8.3 - v600 and
> v603: http://jdbc.postgresql.org/changes.html and that concerns me. Is
> there a patched version of the latest driver? Or will that have to be
It was someone on the list who told me about the patch, I dont know the
situation of the patch at the current moment. I am using the patch on an
PG 8.2.7, and it works fine.
> 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
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: tfinneid@student.matnat.uio.no, scott@richrelevance.com, scott.marlowe@gmail.com, craig@postnewspapers.com.au
Subject: Re: slow update of index during insert/copy
In-Reply-To: <48BC5178.60906@ifi.uio.no>
* 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