Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The point is that another backend's entry could be in a different
> *server* encoding, and what do you do if there's no equivalent
> character in your encoding?
My first thought was that it was just a matter of picking a
character to represent the "unprintable" characters. My second
thought was that if you don't understand the encoding scheme, you're
not even going to know where the character boundaries are. :-(
-Kevin
