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-06 17:51:07
Message-ID: 12129.1244310667@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:
>> you will need to whip up a special-purpose quoting subroutine.

> OK, I see that. I assume I need to care for encoding issues? If so, do I
> assume server encoding or client encoding?

Hoo, good point. You can assume the database (server) encoding, because
that's what the local encoding is from the point of view of libpq ---
and the code in conninfo_parse knows nothing of encodings anyway. So
that's a no-op as far as the quoting itself goes. But that reminds me,
weren't you going to add something to force libpq to set client_encoding
to the database encoding?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Mielke 2009-06-06 17:55:34 Re: PostgreSQL Developer meeting minutes up
Previous Message Joe Conway 2009-06-06 17:42:24 Re: [Fwd: Re: dblink patches for comment]