Re: Impact of UNICODE encoding on performance

From: "M(dot) Bastin" <marcbastin(at)mindspring(dot)com>
To: Harry Mantheakis <harry(at)mantheakis(dot)freeserve(dot)co(dot)uk>
Cc: <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Impact of UNICODE encoding on performance
Date: 2004-03-18 11:21:15
Message-ID: a06020400bc7f355a837a@[192.168.0.101]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

With UNICODE UTF-8 the basic (a-z, A-Z, 0-9, ...) 128 characters
(there are actually less than 128) are single byte characters
identical to the original ASCII specification. All other characters
might have multiple bytes.

This means that as long you are transferring roman alphabet based
text, the impact will be very low since the text will mostly consist
of those 128 characters.

for other languages more characters consisting of multiple bytes
would be transferred.

I don't know about PostgreSQL's internal treatement of multi-byte
characters and whether this woud require more CPU time.

After weighing pro and cons, I'd definitely go with UNICODE.

Marc

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2004-03-18 16:09:50 Re: books
Previous Message Tom Allison 2004-03-18 11:07:56 Re: books