"Craig James" <craig_james@emolecules.com> writes:
> Gregory Stark wrote:
>
>> 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.
>
> You're jumping ahead. This problem has not been accurately diagnosed yet. It
> could be that the pthreads issue is completely misleading everyone, and in fact
> there is a genuine memory corruption going on here. Or not. We don't know yet.
> I have made zero progress fixing this problem.
Well, no that would be you jumping ahead then... You proposed Postgres
changing the way it handles threaded libraries based on Tom's suggestion that
your problem was something like the glibc problem previously found. My comment
was based on the known glibc problem. From what you're saying it's far from
certain that the problem would be fixed by changing Postgres's behaviour in
the way you proposed.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
