Re: libgcc double-free, backend won't die
От | Gregory Stark |
---|---|
Тема | Re: libgcc double-free, backend won't die |
Дата | |
Msg-id | 877ijeqzd9.fsf@oxford.xeocode.com обсуждение исходный текст |
Ответ на | Re: libgcc double-free, backend won't die (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: libgcc double-free, backend won't die
|
Список | pgsql-performance |
"Tom Lane" <tgl@sss.pgh.pa.us> writes: > James Mansion <james@mansionfamily.plus.com> writes: >> Is there any particular reason not to ensure that any low-level >> threading support in libc is enabled right >> from the get-go, as a build-time option? > > Yes. > 1) It's of no value to us > 2) On many platforms there is a nonzero performance penalty And the only reason to do that would be to work around one bug in one small range of glibc versions. If you're going to use a multi-threaded library (which isn't very common since it's hard to do safely for all those other reasons) surely using a version of your OS without any thread related bugs is a better idea. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support!
В списке pgsql-performance по дате отправления: