Re: PQputCopyData dont signal error
От | Andrew Dunstan |
---|---|
Тема | Re: PQputCopyData dont signal error |
Дата | |
Msg-id | 53398FA5.9080204@dunslane.net обсуждение исходный текст |
Ответ на | Re: PQputCopyData dont signal error (steve k <steven.c.kohler@nasa.gov>) |
Ответы |
Re: PQputCopyData dont signal error
|
Список | pgsql-hackers |
On 03/31/2014 10:18 AM, steve k wrote: > <http://postgresql.1045698.n5.nabble.com/file/n5798002/PG_man_excerpt.png> > > > These were my results: > > <http://postgresql.1045698.n5.nabble.com/file/n5798002/PG_embedded_copy_log_excerpt.png> > > > I'd advise anyone contemplating using this feature to seriously seriously > seriously test this and examine your logs after each test run before you > move this feature into your baseline. Maybe you'll have better luck than I > did. You appear not to have understood what you have been told. Specifically Tom Lane's remarks: > PQputCopyData/PQputCopyEnd are only concerned with transferring data. > After you're done with that, you should call PQgetResult to find out the > COPY command's completion status. You should get PGRES_COMMAND_OK, > otherwise it'll be an error result. Neither of these is supposed to return -1 if there's a COPY error, only if there's a data transfer error. Plenty of people have made this work just fine. cheers andrew
В списке pgsql-hackers по дате отправления: