Skip site navigation (1) Skip section navigation (2)

Re: Problem with setlocale (found in libecpg) [accessing a

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

In response to

Responses

pgsql-hackers by date

Next:From: Alex PilosovDate: 2001-09-27 04:08:51
Subject: Re: Spinlock performance improvement proposal
Previous:From: D. HagemanDate: 2001-09-27 03:41:39
Subject: Re: Spinlock performance improvement proposal

pgsql-patches by date

Next:From: Christof PetigDate: 2001-09-27 07:26:12
Subject: Re: [PATCHES] Problem with setlocale (found in libecpg) [accessing a
Previous:From: JustinDate: 2001-09-27 03:44:58
Subject: Re: More fixes for missing double quotes in the shell scripts

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group