DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Xjq5mhzWZC3giOSDqH65tB7g4ue5ro9+tdul5/z81YAedYs2Y196iVqVGGKY5b4XgV56YBSN1ew1SmTtv69KijBsF/FgATPkrGOmmkTcDPdYYGLo5v7OXrUEHv053cGvvHbToFt+0vkCUXltcGdYOZg3HKQL6ZB//RC5znbxlrg=
Message-ID: <1efd553a050719132836c31b78@mail.gmail.com>
Date: Tue, 19 Jul 2005 16:28:26 -0400
From: Oliver Crosby <ryusei@gmail.com>
Reply-To: Oliver Crosby <ryusei@gmail.com>
To: Dawid Kuroczko <qnex42@gmail.com>
Subject: Re: Looking for tips
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>,
	jd@commandprompt.com, pgsql-performance@postgresql.org
In-Reply-To: <758d5e7f0507191319636afaa3@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <s2dd0700.023@gwmta.wicourts.gov>
	<1efd553a0507191308219a098b@mail.gmail.com>
	<758d5e7f0507191319636afaa3@mail.gmail.com>

> If it is possible try:
> 1) wrapping many inserts into one transaction
> (BEGIN;INSERT;INSERT;...INSERT;COMMIT;).  As PostgreSQL will need to
> handle less transactions per second (each your insert is a transaction), =
it
> may work faster.

Aye, that's what I have it doing right now. The transactions do save a
HUGE chunk of time. (Cuts it down by about 40%).

> 2) If you can do 1, you could go further and use a COPY command which is
> the fastest way to bulk-load a database.

I don't think I can use COPY in my case because I need to do
processing on a per-line basis, and I need to check if the item I want
to insert is already there, and if it is, I need to get it's ID so I
can use that for further processing.