Re: BUG #6086: Segmentation fault - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6086: Segmentation fault
Date
Msg-id 13571.1311703637@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #6086: Segmentation fault  (noordsij <noordsij@cs.helsinki.fi>)
Responses Re: BUG #6086: [SOLVED] Segmentation fault  (noordsij <noordsij@cs.helsinki.fi>)
List pgsql-bugs
noordsij <noordsij@cs.helsinki.fi> writes:
> After a few hours of watching strange things happening I finally stumbled
> on the cause.

> Very short summary: the postgres binary needs to be linked to libpthread,
> as this will ensure a special fork() inside libthr (the FreeBSD libpthread
> implementation/wrapper) is used which correctly deals with any pthread
> usage (I am guessing especially statically initialized pthread_X variables
> in for example libxml2).

> This can be accomplished by adding "-lpthread" to the LDFLAGS when building
> either libxml2 or postgresql itself, or by preloading libpthread.so when
> starting postgresql.

Linking pthreads into the backend is likely to cause more problems than
it solves, especially if you're proposing that we do that everywhere.

            regards, tom lane

pgsql-bugs by date:

Previous
From: noordsij
Date:
Subject: Re: BUG #6086: Segmentation fault
Next
From: Greg Johnson
Date:
Subject: Re: BUG #6127: pg_restore failing: unexpected message type 0x58 during COPY from stdin