Re: bytea encode performance issues

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Sim Zacks <sim(at)compulab(dot)co(dot)il>, pgsql-general(at)postgresql(dot)org
Subject: Re: bytea encode performance issues
Date: 2008-08-07 14:35:38
Message-ID: 20080807143538.GC4171@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Merlin Moncure escribió:

> er, I see the problem (single piece of text with multiple encodings
> inside) :-). ok, it's more complicated than I thought. still, you
> need to convert the email to utf8. There simply must be a way,
> otherwise your emails are not well defined. This is a client side
> problem...if you push it to the server in ascii, you can't use any
> server side text operations reliably.

I think the solution is to get the encoding from the email header and
the set the client_encoding to that. However, as soon as an email with
an unsopported encoding comes by, you are stuck.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sim Zacks 2008-08-07 14:40:14 Re: bytea encode performance issues
Previous Message Tom Tom 2008-08-07 14:18:17 pg_restore fails on Windows