Skip site navigation (1) Skip section navigation (2)

Re: BUG #6086: Segmentation fault

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: noordsij <noordsij(at)cs(dot)helsinki(dot)fi>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6086: Segmentation fault
Date: 2011-07-26 18:07:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
noordsij <noordsij(at)cs(dot)helsinki(dot)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 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

In response to


pgsql-bugs by date

Next:From: noordsijDate: 2011-07-26 22:23:07
Subject: Re: BUG #6086: [SOLVED] Segmentation fault
Previous:From: Greg JohnsonDate: 2011-07-26 17:56:55
Subject: Re: BUG #6127: pg_restore failing: unexpected message type 0x58 during COPY from stdin

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group