Tino Wildenhain <[EMAIL PROTECTED]> writes:
> Alban Hertroys schrieb:
>> Matthew T. O'Connor wrote:
>>
>>> Well, to answer my own question, I hacked the source code of DBMail
>>> and had it set the client encoding to LATIN1 immediately after
>>> database connect, this seems to have fixed the problem.
>> LATIN1 != UTF-8. Your problem isn't solved yet.
>>
>
> Well, this enables postgres to translate the encoding.
> However I would be unsure if dbmail always sends latin-1
> anyway.
I would think it would (at least potentially) vary with each message.
The dbmail software should really set client_encoding based on the
Content-Transfer-Encoding header in the message (or whatever it's
called).
LATIN-1 is one of the most common encodings for email but it's
scarcely the only one...
-Doug
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
