Re: CHAR SETS

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: CHAR SETS
Дата
Msg-id 87odf0sr5m.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Re: CHAR SETS  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Список pgsql-general
"Albe Laurenz" <laurenz.albe@wien.gv.at> writes:

> Cesar Alvarez wrote:
>> I got a question, what are the differences of SQL_ASCII and UTF8, witch
>> one should i use??
> SQL_ASCII is ASCII without encoding checks, UTF8 is UTF-8.
> I think that you should use UTF8.

Pros: UTF8 will let you handle other character sets later on (though Postgres
won't be able to provide locale support for more than one locale at the same
time :( )

Cons: UTF8 is slower for many things, especially LIKE and regexp matching. If
you have a very large database you may not be concerned with cpu usage though.
It also requires extra indexes if you want to be able to use an index for
LIKE. And you can't do substring() or length() on a very large datum without
fetching the whole datum.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

В списке pgsql-general по дате отправления:

Предыдущее
От: Gregory Stark
Дата:
Сообщение: Re: Using case expressions in update set clause
Следующее
От: Laurent ROCHE
Дата:
Сообщение: Re : pg_dump - schema diff compatibility