| 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 12:40:47 |
| Message-ID: | 26232.1083847247@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:
> Which takes a lot of time the reason is that in every indchar_lt
> function call SPI connection is made and destroyed...
I cannot imagine how you'd think that that would be practical from a
performance standpoint.
> Here is the problem which i found in postgresql...
> after setting collating sequence in proper way(i.e. C) the order was
> on basis of unicode values...but in Hindi Language some of combined
> unicode values makes a single character
> similarly length is not appropriate for these reasons & hence
> substring operations
Why don't you just use a Hindi locale? The infrastructure should all be
there already for you.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-06 13:02:30 | Fixing the Turkish problem |
| Previous Message | Thomas Hallgren | 2004-05-06 12:17:01 | Re: SPI_fnumber is case sensitive |