Re: Very long SQL strings - Mailing list pgsql-performance

From Steven Flatt
Subject Re: Very long SQL strings
Date
Msg-id 357fa7590706211309w3bc072s321e546f4c5fd976@mail.gmail.com
Whole thread Raw
In response to Re: Very long SQL strings  (Andreas Kretschmer <akretschmer@spamfence.net>)
List pgsql-performance
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
 

pgsql-performance by date:

Previous
From: Bill Moran
Date:
Subject: Re: Database-wide VACUUM ANALYZE
Next
From: "Steven Flatt"
Date:
Subject: Re: Database-wide VACUUM ANALYZE