t is only constructed once. This would alleviate
the immediate problem from my viewpoint.
If you would like more information, I do have the problem reproduced here
in a controlled environment and would love nothing more than to test
patches or provide whatever information might be helpful to fix this
On Aug 19, 2010, at 3:24 PM, Tom Lane wrote:
> Steven Schlansker writes:
>>
>> I'm not at all experienced with character encodings so I could
>> be totally off base, but isn't it wrong to ever call isspace(0x85),
>> whatever the result may be, given that
On Aug 19, 2010, at 2:35 PM, Tom Lane wrote:
> Steven Schlansker writes:
>> I'm having a rather annoying problem - a particular string is causing the
>> Postgres COPY functionality to lose a byte, causing data corruption in
>> backups and transferred data.
>
>
ep me on the CC for replies.
I would very much appreciate help tracking this down! Thanks for your time :)
Steven Schlansker
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
