From: Rod Taylor <pg@rbt.ca>
To: Robert Creager <Robert_Creager@LogicalChaos.org>
Cc: Brock Henry <brock.henry@gmail.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Insert performance, what should I expect?
Date: Wed, 20 Oct 2004 13:20:19 -0400
Message-ID: <1098292819.747.188.camel@home> (raw)
In-Reply-To: <20041020104527.14927c06@thunder.mshome.net>
References: <97b3fe2041019185337a8c3d8@mail.gmail.com>
<1098238348.747.20.camel@home>
<20041020104527.14927c06@thunder.mshome.net>
On Wed, 2004-10-20 at 12:45, Robert Creager wrote:
> When grilled further on (Tue, 19 Oct 2004 22:12:28 -0400),
> Rod Taylor <pg@rbt.ca> confessed:
>
> > > I've done some manual benchmarking running my script 'time script.pl'
> > > I realise my script uses some of the time, bench marking shows that
> > > %50 of the time is spent in dbd:execute.
> > >
> > 1) Drop DBD::Pg and switch to the Pg driver for Perl instead (non-DBI
> > compliant) which has functions similar to putline() that allow COPY to
> > be used.
>
> COPY can be used with DBD::Pg, per a script I use:
>
> $dbh->do( "COPY temp_obs_$band ( $col_list ) FROM stdin" );
> $dbh->func( join ( "\t", @data ) . "\n", 'putline' );
> $dbh->func( "\\.\n", 'putline' );
> $dbh->func( 'endcopy' );
Thanks for that. All of the conversations I've seen on the subject
stated that DBD::Pg only supported standard DB features -- copy not
amongst them.
> With sets of data from 1000 to 8000 records, my COPY performance is consistent
> at ~10000 records per second.
Well done.
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: pg@rbt.ca, Robert_Creager@LogicalChaos.org, brock.henry@gmail.com
Subject: Re: Insert performance, what should I expect?
In-Reply-To: <1098292819.747.188.camel@home>
* 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