Content-Type: text/plain;
  charset="iso-8859-1"
From: Gary Stainburn <gary.stainburn@ringways.co.uk>
Organization: Ringways Garages Ltd
To: Oleg Samoylov <olleg@telecom.mipt.ru>, pgsql-sql@postgresql.org
Subject: Re: Insert multiple Rows
Date: Tue, 4 Mar 2003 11:19:30 +0000
User-Agent: KMail/1.4.3
References: <6f079210.0303030838.21f184af@posting.google.com>
	<b420lg$1um4$1@news.hub.org>
In-Reply-To: <b420lg$1um4$1@news.hub.org>
MIME-Version: 1.0
Message-Id: <200303041119.30866.gary.stainburn@ringways.co.uk>
Content-Transfer-Encoding: quoted-printable

On Tuesday 04 Mar 2003 10:54 am, Oleg Samoylov wrote:
> Hi,
>
> Saint X wrote:
> > Hi, I have a program that need to send a Postgresql database a lot of
> > rows, i'm doing it using FOR an INSERT, something like this
> > for i =3D 0 to 1000
> > {
> >  insert into table(item1) VALUES (i);
> > }
> >
> > And so on, as you can imagine these consume a lot of resources and
> > move so slowly, that's why I'm looking for a command to send more than
> > one row at the time, something like
> >
> > insert into table (item1) values ('1' / '2' / '3' / '4' ... / '1000');
>
> You can do instead:
>
> insert into table (item1) values ('1');
> insert into table (item1) values ('2');
> ....
> insert into table (item1) values ('1000');
>
> As single query.
>
> But better use COPY command or prepared statment.
>
> Inserts slow commonly due to indexis and foreing keys.

If you use a 'prepared' insert within a transaction, would that speed thing=
s=20
up - maybe by defering index updates?
--=20
Gary Stainburn
=20
This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000=20=
=20=20=20=20