Re: Thread-unsafe coding in ecpg

Поиск
Список
Период
Сортировка
От Michael Meskes
Тема Re: Thread-unsafe coding in ecpg
Дата
Msg-id 907962be808367ff475893ce07a8442700e3e65a.camel@postgresql.org
обсуждение исходный текст
Ответ на Re: Thread-unsafe coding in ecpg  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Thread-unsafe coding in ecpg  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
> While (b) has more theoretical purity, I'm inclined to think it
> doesn't really improve anybody's life compared to (a), because
> --disable-thread-safety doesn't actually stop anyone from using
> libpq or ecpglib in threaded environments.  It just makes it
> more likely to fail when they do.

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?

We could also rewrite the parsing of numbers to not be locale
dependent.

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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Gierth
Дата:
Сообщение: Re: pg_stat_statements vs. SELECT FOR UPDATE
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pg_stat_statements vs. SELECT FOR UPDATE