From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Frits Jalvingh <jal(at)etc(dot)to> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Kenneth Marshall <ktm(at)rice(dot)edu>, Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Improving PostgreSQL insert performance |
Date: | 2017-06-11 04:15:18 |
Message-ID: | b58fb564-5edf-172c-7c9c-76a7654373b0@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 06/10/2017 07:32 PM, Alvaro Herrera wrote:
> Frits Jalvingh wrote:
>
>> So, I am still very interested in getting normal inserts faster, because
>> that will gain speed for all work.. If Oracle can do it, and Postgres is
>> able to insert fast with copy- where lies the bottleneck with the insert
>> command? There seems to be quite a performance hit with the JDBC driver
>> itself (as the stored procedure is a lot faster), so I can look into that.
>> But even after that there is quite a gap..
>
> Did you try inserting multiple tuples in one command? Something like
> INSERT INTO .. VALUES ('col1', 'col2'), ('col1', 'col2'), ('col1', 'col2')
> It's supposed to be faster than single-row inserts, though I don't
> know by how much.
When I did the testing of the patch originally I saw significant
improvements, e.g. 8x in early versions. The thread is here:
https://www.postgresql.org/message-id/flat/44C4451A(dot)4010906%40joeconway(dot)com#44C4451A(dot)4010906(at)joeconway(dot)com
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
From | Date | Subject | |
---|---|---|---|
Next Message | Frits Jalvingh | 2017-06-11 08:44:04 | Re: Improving PostgreSQL insert performance |
Previous Message | Alvaro Herrera | 2017-06-11 02:32:14 | Re: Improving PostgreSQL insert performance |