From: | Marko Kreen <markokr(at)gmail(dot)com> |
---|---|
To: | Nicolas Grilly <nicolas(at)gardentechno(dot)com> |
Cc: | Federico Di Gregorio <federico(dot)digregorio(at)dndg(dot)it>, psycopg(at)postgresql(dot)org |
Subject: | Re: copy_from does not stop reading after an error |
Date: | 2011-02-08 12:52:50 |
Message-ID: | AANLkTi=JywGtY_+2M-fs79gM6kUCozdQ-728r5YpNdBx@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On Tue, Feb 8, 2011 at 2:38 PM, Nicolas Grilly <nicolas(at)gardentechno(dot)com> wrote:
> On Tue, Feb 8, 2011 at 13:30, Marko Kreen <markokr(at)gmail(dot)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.
It's the high point of the of last flame^Wcommitfest for 9.1,
so it may take some time.
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2011-02-08 12:53:17 | Re: copy_from does not stop reading after an error |
Previous Message | Nicolas Grilly | 2011-02-08 12:38:20 | Re: copy_from does not stop reading after an error |