Invalid Byte Sequence For Encoding Utf8 0x00

Invalid Byte Sequence For Encoding Utf8 0X00. CREATE OR REPLACE FUNCTION blob2text() RETURNS void AS $$ Declare ref record i integer Begin FOR ref IN SELECT id blob_field FROM table LOOP find 0x00 and replace with space i = position(E&#39\\000&#39bytea in refblob_field) WHILE i > 0 LOOP refbob_field = set_byte(refblob_field i1 20) i = position(E&#39\\000&#39bytea in refblobl_field) END LOOP UPDATE table SET field = encode(refblob_field &#39escape&#39) WHERE id = refid END LOOP End $$ LANGUAGE plpgsql.

results in ERROR invalid byte sequence for encoding “UTF8” 0x00 I looked into this and it seems Postgres doesn&#39t like the NULL character \00 in text fields Most of the existing advice online on this error are for people seeing errors inserting data into Postgres In which case the fix seems to be to filter the null character prior to the insert.

invalid byte sequence for encoding "UTF8": 0x00 · Issue #1422

> ERROR invalid byte sequence for encoding “UTF8” 0x00 > > CONTEXT converting column cname for foreign table scan of > ora_fdw_schemacust_names row 122 The reason is that there are some zero bytes (ASCII NUL) in the Oracle table While these are allowed in Oracle they are not allowed in PostgreSQL Date 20171107 074114MessageID 1510040474284541camel@cybertecat.

Postgres error on insert ERROR: invalid byte sequence for

ERROR invalid byte sequence for encoding “UTF8” 0x00 HINT This error can also happen if the byte sequence does not match the encoding expected by the server which is controlled by “client_encoding” mysqldump in postgresql mode will dump null bytes as \0 in strings so you probably want to search for that sequence of characters.