Re: Migration study, step 1: bulk write performance optimization

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>
Cc: Mikael Carneholm <Mikael(dot)Carneholm(at)WirelessCar(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Migration study, step 1: bulk write performance optimization
Date: 2006-03-21 00:27:17
Message-ID: 9396.1142900837@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Craig A. James" <cjames(at)modgraph-usa(dot)com> writes:
> If you haven't explored the COPY command yet, check it out. It is stunningly fast compared to normal INSERT commands.

Note also that his "benchmark" is testing multiple INSERTs issued within
a loop in a plpgsql function, which has got nearly nothing to do with
the performance that will be obtained from INSERTs issued by a client
(especially if said INSERTs aren't prepared and/or aren't batched into
transactions).

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jaime Casanova 2006-03-21 01:38:15 Re: update == delete + insert?
Previous Message PFC 2006-03-20 23:27:04 Re: Best OS & Configuration for Dual Xeon w/4GB & Adaptec