| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PQputCopyData dont signal error |
| Date: | 2011-04-14 07:56:24 |
| Message-ID: | BANLkTinBi3fm1+pbWR_UYUTpO=QVx_rdZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
>
> The way COPY works is that PQputCopyData just sends the data to the server,
> and the server will buffer it in its internal buffer and processes it when
> it feels like it. The PQputCopyData() calls don't even need to match line
> boundaries.
>
Yes, it is current behave - then documentation is obsolete
> I think you'll need to send all the data and finish the COPY until you get
> an error. If you have a lot of data to send, you might want to slice it into
> multiple COPY statements of say 50MB each, so that you can catch errors in
> between.
:( I wold to import table in one statement
Regards
Pavel Stehule
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-04-14 11:48:47 | Re: Itanium HP-UX build failure, register stack |
| Previous Message | Heikki Linnakangas | 2011-04-14 07:50:16 | Re: PQputCopyData dont signal error |