| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Collation rules and multi-lingual databases |
| Date: | 2003-08-23 15:41:10 |
| Message-ID: | 20030823083122.K24780-100000@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23 Aug 2003, Greg Stark wrote:
> Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
>
> > Since most of that work is for an exceptional case, maybe it'd be safer
> > (although slower) to structure the function as
>
> Yeah I thought of that. But if making it a critical section is cheap then it's
> probably a better approach. The problem with restoring the locale for the
> palloc is that if the user is unlucky he might sort a table of thousands of
> strings that all trigger the exception case.
True. I still worry about the critical section since an error will cause
the entire database system to restart, but as I'd also forgotten about
signals which might cause problems (uncertain without looking) I'm not
sure you have a good alternative even not counting the speed issues.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2003-08-23 16:12:15 | Re: Collation rules and multi-lingual databases |
| Previous Message | Anastasios Hatzis | 2003-08-23 15:02:29 | Surveys & Studies: FLOSS - Usage of Free/Libre Open Source Software (PostgreSQL, etc.) |