| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christof Petig <christof(at)petig-baender(dot)de> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Problem with setlocale (found in libecpg) [accessing a |
| Date: | 2001-09-27 04:08:29 |
| Message-ID: | 15361.1001563709@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
>> Well at least on glibc-2.2 it seems that setlocale retuns a pointer to
>> malloced memory, and frees this pointer on subsequent calls to
>> setlocale.
>> So I would kindly ask you to take a second look at every invokation of
>> setlocale.
I looked around, and am worried about the behavior of PGLC_current()
in src/backend/utils/adt/pg_locale.c. It doesn't change locale but
does retrieve several successive setlocale() results. Does that work
in glibc?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Pilosov | 2001-09-27 04:08:51 | Re: Spinlock performance improvement proposal |
| Previous Message | D. Hageman | 2001-09-27 03:41:39 | Re: Spinlock performance improvement proposal |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christof Petig | 2001-09-27 07:26:12 | Re: [PATCHES] Problem with setlocale (found in libecpg) [accessing a |
| Previous Message | Justin | 2001-09-27 03:44:58 | Re: More fixes for missing double quotes in the shell scripts |