Re: [Fwd: Re: dblink patches for comment]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [Fwd: Re: dblink patches for comment]
Date: 2009-06-07 01:31:43
Message-ID: 2557.1244338303@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> Tom Lane wrote:
>> But that reminds me, weren't you going to add something to force
>> libpq to set client_encoding to the database encoding?

> I think the attached is what you had in mind.

Looks plausible to me.

> But I don't know right off
> 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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-06-07 02:26:12 Re: pg_migrator issue with contrib
Previous Message Joe Conway 2009-06-07 01:23:13 Re: [Fwd: Re: dblink patches for comment]