Re: copy_from does not stop reading after an error
| От | Nicolas Grilly |
|---|---|
| Тема | Re: copy_from does not stop reading after an error |
| Дата | |
| Msg-id | AANLkTin6mBtLmvOuw2SW7=iAnoO8sC3FNNH+bWj_=-2p@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: copy_from does not stop reading after an error (Marko Kreen <markokr@gmail.com>) |
| Ответы |
Re: copy_from does not stop reading after an error
Re: copy_from does not stop reading after an error |
| Список | psycopg |
On Tue, Feb 8, 2011 at 13:30, Marko Kreen <markokr@gmail.com> wrote:
Yeah, seems your analysis is right and it's libpq (design?) bug,
so no way to work around it.
Nice to know that my analysis is right... but eventually it is a bad news because the only way to fix the issue is to split input data into many chunks or to directly modify libpq... By the way, I have posted my analysis to pgsql-hackers and asked what the list thinks about modify pqParseInput to handle this case. But I have never posted to this list before so I don't know what is the good way to ask for feedback.
Nicolas Grilly
В списке psycopg по дате отправления: