| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Greg Smith" <greg(at)2ndQuadrant(dot)com>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: procpid? |
| Date: | 2011-06-16 16:56:50 |
| Message-ID: | 4DF9EF82020000250003E74D@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-06-16 16:58:16 | Re: Why polecat and colugos are failing to build back branches |
| Previous Message | Bernd Helmle | 2011-06-16 16:56:17 | Re: procpid? |