Re: dangers of setlocale() in backend (was: problem with float8 input format)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ldm(at)apartia(dot)ch
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: dangers of setlocale() in backend (was: problem with float8 input format)
Date: 2000-08-12 17:10:01
Message-ID: 23129.966100201@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Louis-David Mitterrand <cunctator(at)apartia(dot)ch> writes:
>> IMPORTANT: changing the backend's locale on-the-fly is an EXTREMELY
>> DANGEROUS thing to do, and I strongly recommend that you find another
>> way to solve your problem.

> The "problem" I am trying to solve is to send e-mail notifications to
> auction bidders in their own language with the proper number formatting,
> etc. From what you are saying I'll probably have to move these
> notifications to the mod_perl layer of the application.

Well, you could fork a subprocess to issue the mail and change locale
only once you're safely inside the subprocess.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-08-12 17:45:46 Re: [HACKERS] Optimizer confusion?
Previous Message Byron Nikolaidis 2000-08-12 16:55:25 Re: ClassNotFoundException

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-08-12 17:45:46 Re: [HACKERS] Optimizer confusion?
Previous Message Louis-David Mitterrand 2000-08-12 16:51:06 dangers of setlocale() in backend (was: problem with float8 input format)