Re: [Fwd: Re: dblink patches for comment] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [Fwd: Re: dblink patches for comment]
Date
Msg-id 12129.1244310667@sss.pgh.pa.us
Whole thread Raw
In response to Re: [Fwd: Re: dblink patches for comment]  (Joe Conway <mail@joeconway.com>)
Responses Re: [Fwd: Re: dblink patches for comment]  (Joe Conway <mail@joeconway.com>)
Re: [Fwd: Re: dblink patches for comment]  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Joe Conway <mail@joeconway.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


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: [Fwd: Re: dblink patches for comment]
Next
From: Mark Mielke
Date:
Subject: Re: PostgreSQL Developer meeting minutes up