Joe Conway <[EMAIL PROTECTED]> writes:
> (gdb) bt
> #0 pg_verifymbstr (mbstr=0x837a698 "42", len=2) at wchar.c:541
> #1 0x08149c26 in textin (fcinfo=0xbfffeca0) at varlena.c:191
> #2 0x08160579 in DirectFunctionCall1 (func=0x8149c00 ,
> arg1=137864856) at fmgr.c:657
> #3 0x080bbffa in update_
> [EMAIL PROTECTED] writes:
> > If a byte string that is not valid unicode is inserted into a bytea
> > column, analyze will fail unless the data was tagged as bytea in the
> > insert.
>
> Your example produces no failure for me. You'd better be more specific
> about which PG version you're runn
[EMAIL PROTECTED] writes:
> If a byte string that is not valid unicode is inserted into a bytea
> column, analyze will fail unless the data was tagged as bytea in the
> insert.
Your example produces no failure for me. You'd better be more specific
about which PG version you're running, on what p
Anders Hammarquist ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Interactions between bytea and character encoding when doing analyze
Long Description
If a byte string that is not valid unicode is inserted into a bytea
column
