| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Thread-unsafe coding in ecpg |
| Date: | 2019-01-20 17:08:40 |
| Message-ID: | d441f5913b147e5b3e0eed4647f9839d926d90fc.camel@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > The question is, what do we do on those platforms? Use setlocale()
> > or
> > fallback to (a) and document that ecpg has to run in a C locale?
>
> No, we shouldn't use setlocale(), because it clearly is hazardous
> even on platforms where it doesn't fail outright. I don't see
> anything so wrong with just documenting the hazard. The situation
Actually I meant using setlocale() and documenting that it must not be
used with threads, or document it must not be used with locales?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-01-20 17:13:04 | Re: shared-memory based stats collector |
| Previous Message | Pavel Stehule | 2019-01-20 16:55:41 | Re: PostgreSQL vs SQL/XML Standards |