Re: utf8 errors - Mailing list pgsql-general

From Albe Laurenz
Subject Re: utf8 errors
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17BB6FEC@ntex2010a.host.magwien.gv.at
Whole thread Raw
In response to Re: utf8 errors  (Jiří Pavlovský <jiri@pavlovsky.eu>)
Responses Re: utf8 errors  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Jirí Pavlovský wrote:
>>> I'm getting these errors on tables as
>>> well. Actually when I copy and paste the offending queries from log into pgAdmin it runs without an
>>> error.

>> So the queries work from pgadmin; what application/environment are they NOT working in?
>> Something is obviously different. You say it's a Win32 application, what database libraries and
>> programming languages are involved?

> I'm using  plain c and libpq from 9.2.2. And gtk as a GUI. Compiler is mingw (gcc for windows).

>> Does the application perhaps send trailing garbage after the query or something similar?
>> Something like that might happen if there's a memory allocation bug in the application.
>> I'm assuming here that, if the query string cannot be converted from utf-8 due to garbage
>> characters, the transcoding error triggers before the query parser notices a syntax error.

> Could be. But when I look at the query string in gdb, before it is send, I don't see there anything
> problematic.
> I guess I'll have to try to wite some test cases to try to locate the problem.

Once you can reproduce the problem, try a network trace on the communication
between cleint and server.  Maybe that helps to solve the problem.

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: Jiří Pavlovský
Date:
Subject: Re: utf8 errors
Next
From: dafNi zaf
Date:
Subject: dynamic partitioning