Bug in PGSQL 9.0 with handling chr(1..255) in Win1250 context?

Hi!

Windows 7x64, PG9.0, PGAdmin 1.12.1.

First I sent this problem to PGADMIN support list, you can see it, but
I repeat the description.

http://archives.postgresql.org/pgadmin-support/2011-04/msg00012.php

I tried to fillup a text field with all ANSI characters
chr(1)..chr(255). Except 0 because it is string limitator in C.

This experience is based on that I want to check, how the row encoded
in "Backup" (how to COPY eat this).

But when I tried to see the row in PGADMIN, I got this error:

ERROR: character 0x81 of encoding "WIN1250" has no equivalent in "UTF8"

********** Error **********

ERROR: character 0x81 of encoding "WIN1250" has no equivalent in "UTF8"
SQL state: 22P05

I reported this to PGADMIN list, but Dave said:

That error comes from PostgreSQL, and is entirely expected if you try
to store non-printable characters in a text column, and then convert
it to UTF-8 (which is what happens when pgAdmin requests data).
PostgreSQL is extremely strict about enforcing the correctness of
unicode data.

Interesting thing that I have Win1250 context with Win1250 db.

I think that is unacceptable to cannot see the row.

EMS PG Manager can show the row, but may it do something in other way
- I don't know.

Thanks:
dd