Joe Conway <m...@joeconway.com> writes:
> Tom Lane wrote:
>> Hmm. You can presumably fix this by setting client_encoding in the
>> dblink connection to match the encoding in use in the database it's
>> called in. But I wonder why dblink doesn't just do that for you
>> automatically.
> But if you think automatically setting client encoding is appropriate, I
> will make the change. Would it be classified as a bug (and therefore
> something to backpatch) or a new feature?
You could make an argument either way; but given that we're not seeing
vast demand in this thread, I think I'd vote for not changing behavior
in the back branches. It'd be good to get it into 8.4 though.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
