| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vinay Jain <vinayj(at)sarathi(dot)ncst(dot)ernet(dot)in> |
| Cc: | Andrew Hammond <ahammond(at)ca(dot)afilias(dot)info>, vinayj(at)ncst(dot)ernet(dot)in, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Is there any method to keep table in memory at startup |
| Date: | 2004-05-06 14:32:21 |
| Message-ID: | 28455.1083853941@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vinay Jain <vinayj(at)sarathi(dot)ncst(dot)ernet(dot)in> writes:
> Not actually even in Hindi Locale the output was incorrect..i.e. sort
> order was wrong
> and also length and substring operations
> which are not based on syllables.
Hm, possibly you weren't using the same character set encoding that the
locale was expecting? It's not very well documented, but every locale
setting works only with a specific encoding.
If the locale definition really is wrong for your purposes, it seems
like what you want to do is write a new locale definition that does what
you want. Then you could use it with any Unix program, not only
Postgres. (I've never done this, but I can't see that it would be any
harder than writing C code inside Postgres to do it ...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2004-05-06 14:38:30 | Re: More Hashing questions |
| Previous Message | Tom Lane | 2004-05-06 14:28:56 | Re: initdb failure in CVS |