| From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
|---|---|
| To: | eildert(dot)groeneveld(at)fli(dot)bund(dot)de |
| Cc: | Ladislav Lenart <lenartlad(at)volny(dot)cz>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: degrading inser performance |
| Date: | 2015-09-17 14:21:15 |
| Message-ID: | CAJghg4KWkUhkzNeuqkihDCxVBgseJDeCoYni735RwiUOad4-5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Sep 17, 2015 at 9:19 AM, Eildert Groeneveld <
eildert(dot)groeneveld(at)fli(dot)bund(dot)de> wrote:
> > * one COPY per bulk (20 000 rows)
> copy does not fit so well, as it is not only initial populating.
>
Why do you say COPY doesn't fit? It seems to me that COPY fits perfectly
for your case, and would certainly make the load faster.
I suspect (not sure though) that the degradation is most because you are
inserting one row at a time, and, it needs to verify FSM (Free Space Map)
for each tuple inserted, when the table start to get more populated, this
verification starts to become slower. If that is really the case, COPY
would certainly improve that, or even INSERT with many rows at once.
Regards,
--
Matheus de Oliveira
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eildert Groeneveld | 2015-09-17 14:41:08 | Re: degrading inser performance |
| Previous Message | Eildert Groeneveld | 2015-09-17 12:19:25 | Re: degrading inser performance |