Skip site navigation (1) Skip section navigation (2)

Choosing character set for database

From: Grzegorz Szpetkowski <gszpetkowski(at)gmail(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Choosing character set for database
Date: 2011-04-20 20:29:58
Message-ID: BANLkTinZ=n9OjTnNM9YX+ciZ0+zxWyxTVQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-novice
Is there any clear performance difference of using multi-byte
character set (such as UTF-8) and single-byte (e.g. SQL_ASCII,
LATIN2). Why there is no UTF-32 (generally more space for chars, but
faster to calculate than multibyte ?) ? I found only at Oracle 11g
documentation that:

"For best performance, choose a character set that avoids character
set conversion and uses the most efficient encoding for the languages
desired. Single-byte character sets result in better performance than
multibyte character sets, and they also are the most efficient in
terms of space requirements. However, single-byte character sets limit
how many languages you can support."

Regards,
Grzegorz Sz.

Responses

pgsql-novice by date

Next:From: Sandy KeathleyDate: 2011-04-20 23:04:00
Subject: Connecting and creating db
Previous:From: Deka, Rajib IN MAA SLDate: 2011-04-20 13:12:48
Subject: Database system identifier mismatch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group