PostgreSQL BugTool Submission

fmatheus (fmatheus(at)consultoria(dot)net) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
trouble with COPY from a iso-8859-1 encoding file

Long Description
Im notice this in pg 6.5.3 in a Debian/linux 2.2 in AMD K7.
if there is some enhancede char like a a acute () in a field than is been imported by copy from, there is some parse error in the next field (in my clase a float4).
That happens just if the latin char is in the last word or is the last char of the field (varchar).
I did a workarround:
if that is the last char, append 2 spaces to the field
if in the last word but not the last char, append just 1 space.
that works, but is strange.

PS: i did not know new version yet, but would be very helpfull if COPY from report the line number at a parse error.

Thanks.

Sample Code

No file was uploaded with this report