| From: | Reece Hart <reece(at)harts(dot)net> |
|---|---|
| To: | SF PostgreSQL <sfpug(at)postgresql(dot)org> |
| Subject: | locale and encoding advice |
| Date: | 2006-08-03 22:48:21 |
| Message-ID: | 1154645301.16476.302.camel@tallac.gene.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | sfpug |
Does anybody know of an idiot's guide to the ins and outs of selecting
database encoding? I remember reading on pgsql mailing lists about
gotchas when using some choices of locales or encodings with some
postgresql features. I recall that someone -- David Fetter, I think --
wrote something disparaging about SQL_ASCII.
My needs are simple: modern linux (suse 10), x86_64, pg 8.1.4, mostly
American English, occasional use of tsearch2. I don't understand the
tradeoffs between C, SQL_ASCII, UTF8, or any of the other possibilities.
Any recommendations? I'm in SQL_ASCII now, but I'm about to rebuild and
this is a good time to reconsider.
Thanks,
Reece
--
Reece Hart, http://harts.net/reece/, GPG:0x25EC91A0
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-08-03 23:08:12 | Re: locale and encoding advice |
| Previous Message | Casey Duncan | 2006-08-01 18:48:52 | Re: Second annual Harambee!!!! - PostgreSQL @ Linux World - call for volunteers, etc. |