| From: | Nicolas Paris <niparisco(at)gmail(dot)com> |
|---|---|
| To: | 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-10 20:12:35 |
| Message-ID: | 20170610201235.GA8502@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> I tried the copy command, and that indeed works quite brilliantly:
> Inserted 24000000 rows in 22004 milliseconds, 1090710.7798582076 rows per
> second
>
> That's faster than Oracle. But with a very bad interface I have to say for
> normal database work.. I will try to make this work in the tooling, but it
> needs some very special code to format all possible values properly, and to
> manage the end of the copy, so it is not usable in general which is a pity, I
> think.
Have you thought about the COPY with binary format ? Thats looks more
robust than the text format you used in your benchmarks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frits Jalvingh | 2017-06-10 20:37:48 | Re: Improving PostgreSQL insert performance |
| Previous Message | Frits Jalvingh | 2017-06-10 11:12:43 | Re: Improving PostgreSQL insert performance |