| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [Fwd: Re: dblink patches for comment] |
| Date: | 2009-06-07 17:34:46 |
| Message-ID: | 4A2BFA36.701@joeconway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>> how to trigger the failure (and therefore how to test the solution). A
>> naive test with two databases, one LATIN2, the other UTF8 does not
>> produce the error with simple text literals. Any guidance on specific
>> literals that would trigger the problem?
>
> Hmm, sending some non-ASCII characters from the LATIN2 end to the UTF8
> end should do it, I would think. The other direction would probably
> not show any immediate error.
I tried some random high-bit characters on the LATIN2 side, but was not
able to stumble upon the right combination of characters to trigger a
complaint. I've contacted Ruzsinszky Attila off-list and he said he will
get me a self contained test case.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-06-07 17:56:56 | Re: pg_migrator issue with contrib |
| Previous Message | Bruce Momjian | 2009-06-07 17:34:44 | Re: pg_migrator issue with contrib |