"Arun P.L" <arunpl@hotmail.com> writes:
> And the way to deal with this? Any ideas on that?
If you were happy with SQL_ASCII encoding before, keep using it.
Other encoding choices are basically constraints to ensure your
data is valid according to that encoding --- if you don't feel
like trying to clean up the data encoding right now, then don't.
regards, tom lane
