"Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> writes:
> I think this happens when the front-end encoding is SQL_ASCII and the
> database is using UNICODE. Then, there are misunderstandings between
> front-end and back-end, so that a single character with the eighth bit
> set may be sent by the front-end and interpreted by the back-end as the
> first half of a UNICODE two-byte character.
I wondered about that, but his examples had one or more characters
between the eighth-bit-set character and the '|', so this doesn't seem
to explain the problem.
Still, if it went away after moving to ASCII encoding, it clearly is
a multibyte issue of some sort.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: The Hermit Hacker||Date: 2001-02-27 17:26:03|
|Subject: Re: Re: Re: [PATCHES] A patch for xlog.c|
|Previous:||From: Matthew Kirkwood||Date: 2001-02-27 17:17:24|
|Subject: Re: A patch for xlog.c|
pgsql-admin by date
|Next:||From: lbottorff||Date: 2001-02-27 21:55:46|
|Subject: pg_hba.conf changes have no effect on cygwin/NT 4.0|
|Previous:||From: Alfonso Peniche||Date: 2001-02-27 17:01:11|
|Subject: Re: CHAR vs VARCHAR|