From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: performance for high-volume log insertion |
Date: | 2009-04-27 06:29:19 |
Message-ID: | dcc563d10904262329k4c2e4a01p6fb7e684130f8df5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sun, Apr 26, 2009 at 11:07 AM, Kris Jurka <books(at)ejurka(dot)com> wrote:
>
>
> On Thu, 23 Apr 2009, Thomas Kellerer wrote:
>
>> Out of curiosity I did some tests through JDBC.
>>
>> Using a single-column (integer) table, re-using a prepared statement took
>> about 7 seconds to insert 100000 rows with JDBC's batch interface and a
>> batch size of 1000
>>
>
> As a note for non-JDBC users, the JDBC driver's batch interface allows
> executing multiple statements in a single network roundtrip. This is
> something you can't get in libpq, so beware of this for comparison's sake.
Really? I thought that executing statements like so:
select * from a;insert ...;delete;
in psql / libpq would execute them all in one trip.
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2009-04-27 06:45:08 | Re: performance for high-volume log insertion |
Previous Message | Mark Wong | 2009-04-27 03:44:51 | Re: Using IOZone to simulate DB access patterns |