"Pavel Stehule" <pavel.stehule@gmail.com> writes:
> Changes related to convert* functions in postgresql 8.3 has impact on
> to_ascii function.
ISTM to_ascii has a completely bogus API anyway. What is it doing
taking an encoding name as an argument? It should just assume the
input text is in the database encoding.
The real fix that's needed there is to improve the set of encodings
it can deal with ...
regards, tom lane