The following bug has been logged online:

Bug reference: 2175
Logged by: Roberto
Email address: speedrob (AT) pop (DOT) com.br
PostgreSQL version: 8.0
Operating system: windows XP
Description: 22021: invalid byte sequence for encoding \"UNICODE\":
Details:

when I go to insert one string with accent in the bank of the following o
error:
22021: invalid byte sequence for encoding \"UNICODE\":

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

--xXmbgvnjoT4axfJE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 16, 2006 at 11:55:12PM +0000, Roberto wrote:
This usually means that the encoding of your client is not UTF-8. Try
some query like "SET client_encoding TO 'LATIN1'" to see if the problem
disappears. Better yet -- try to convince the client to use UTF-8
encoding.

HTH
-- tomas

--xXmbgvnjoT4axfJE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFDzIHyBcgs9XrR2kYRAjEjAJ4lcCtSs3HNRP4tvkUAF7 SqgXENQwCfdsqt
gQbAgMudnExyxg7u3jul8HM=
=t++h
-----END PGP SIGNATURE-----

--xXmbgvnjoT4axfJE--