[rsyslog] PostgreSQL: Problems with character encoding

[Jakob Haufe]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 20 Jan 2010 10:44:42 -0800 (PST)
david at lang.hm wrote:

> my thought is that just like we have a filter to change control characters 
> to escape sequences, it would be good to have a filter to escape non-ascii 
> characters. this will mangle other character sets, but they are unlikly to 
> go through cleanly anyway.

This is not an escaping issue, but an issue of byte sequences that are not
valid UTF8. That's why PostgreSQL rejects them. So we either need to make
ompgsql set SQL_ASCII as a client encoding (which will result in extended
characters being transcoded to UTF-8, which results in garbage) or make the
database SQL_ASCII.

Regards,
Jakob Haufe (sur5r)

- -- 
ceterum censeo microsoftem esse delendam.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAktYuf0ACgkQ1YAhDic+adY60QCbBqyEzDJtaEiWmg1cqKlMEJ2N
PnwAn2wAfPIpGlCOx2LdPJivrElU83Bu
=eTVw
-----END PGP SIGNATURE-----