From: Steven Flatt <steven.flatt@gmail.com>
To: Andreas Kretschmer <akretschmer@spamfence.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Very long SQL strings
Date: Thu, 21 Jun 2007 16:09:31 -0400
Message-ID: <357fa7590706211309w3bc072s321e546f4c5fd976@mail.gmail.com> (raw)
In-Reply-To: <20070621184833.GA10814@KanotixBox>
References: <357fa7590706211133u2ae43d09id1653ca63d7a7838@mail.gmail.com>
<20070621184833.GA10814@KanotixBox>
Thanks everyone for your responses. I don't think it's realistic to change
our application infrastructure to use COPY from a stream at this point.
It's good to know that multi-row-VALUES is good up into the thousands of
rows (depending on various things, of course). That's a good enough answer
for what I was looking for and we can revisit this if performance does start
to hurt.
On 6/21/07, Andreas Kretschmer <akretschmer@spamfence.net> wrote:
>
> I guess you can obtain the same if you pack all INSERTs into one
> transaction.
Well the 20% gain I referred to was when all individual INSERTs were within
one transaction. When each INSERT does its own commit, it's significantly
slower.
Steve
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: steven.flatt@gmail.com, akretschmer@spamfence.net
Subject: Re: Very long SQL strings
In-Reply-To: <357fa7590706211309w3bc072s321e546f4c5fd976@mail.gmail.com>
* 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