| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: locale |
| Date: | 2004-04-09 05:18:33 |
| Message-ID: | Pine.LNX.4.44.0404090712480.4551-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 8 Apr 2004, Tom Lane wrote:
> Yup, exactly. If we did not force both LC_COLLATE and LC_CTYPE to have
> the same values cluster-wide, then we *would* have index corruption
> issues.
We really show warn people that using another encoding in a database then
what the cluster uses, breaks sorting.
I was under the impression that as long as I've set the right locale when
doing initdb I could then create different databases with different
encodings and it all works, but it does not. I simply trust pg too much
(not without reason since it is an amazing project).
--
/Dennis Björklund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-04-09 06:07:14 | Re: Checking for USAGE on SET search_path... |
| Previous Message | Tom Lane | 2004-04-09 05:11:04 | Re: Small suggestion on build script |