From: | ow <oneway_111(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | New database: SQL_ASCII vs UTF-8 trade-offs |
Date: | 2006-03-07 14:08:24 |
Message-ID: | 20060307140824.73656.qmail@web53902.mail.yahoo.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"PostgreSQL 8.1.0 on i486-pc-linux-gnu, compiled by GCC cc (GCC) 4.0.3 20051111
(prerelease) (Debian 4.0.2-4)"
Hi,
Am having some doubts whether a new db should be with SQL_ASCII or UTF-8
encoding. We expect ALL of our data to be ASCII. At the same time, I guess,
it's possible that some user may decide to get creative and enter, for example,
his own name with non-ASCII chars.
So, it seems that UTF-8 would be a better choise even if we plan to store only
ASCII data (a lot of ASCII data though).
Are there any negative effects related to the selection of UTF-8 over SQL_ASCII
(e.g. size of the database, sort/like/group issues, etc)?
Thanks in advance
---------------------------------------------------------------------------
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-03-07 14:38:11 | Re: New database: SQL_ASCII vs UTF-8 trade-offs |
Previous Message | Joost Kraaijeveld | 2006-03-07 12:54:58 | Can I delete all WAL logfiles if the database is shutdown without errors? |