From: | Dorian Hoxha <dorian(dot)hoxha(at)gmail(dot)com> |
---|---|
To: | Rakesh Kumar <rakeshkumar464(at)outlook(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Multiple inserts |
Date: | 2016-09-23 13:36:39 |
Message-ID: | CANsFX04bvteACkquHPYaMRr+LtnsLDKpkHKUnU=GYDLtvRM8CA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
If the connection is in autocommit, then each statement will also incur a
commit (write to the commit log on disk).
On Fri, Sep 23, 2016 at 2:01 PM, Rakesh Kumar <rakeshkumar464(at)outlook(dot)com>
wrote:
> Hi
>
> I am noticing that if I do this
>
> insert into table values(1,a)
> insert into table values(2,b)
>
> insert into table values(3,c)
> ....
> commit after 500 rows
> it is lot slower (almost 10x) than
> insert into table values((1,a),(2,b),(3,c)) .. upto 500
>
> It is obvious that the gain is due to network trip avoided after every
> insert.
>
> My question is: Are they any known side-effects or drawbacks of using
> multiple inserts. I am aware the error checking is much more difficult in
> the second approach. Any other drawbacks?
>
> thanks
>
From | Date | Subject | |
---|---|---|---|
Next Message | Deven Phillips | 2016-09-23 14:14:57 | jsonb_set for nested new item? |
Previous Message | Rakesh Kumar | 2016-09-23 12:01:49 | Multiple inserts |