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

Re: Multi-threaded user app segfaults when using libpq with separate connections

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Multi-threaded user app segfaults when using libpq with separate connections
Date: 2003-08-04 22:41:02
Message-ID: 13531.1060036862@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> writes:
>> You may care to try your test with CVS tip and see if it works better.

> I've retried this with a cvs-version of this afternoon (local
> time). The build stranded in plpgsql (I seem to need a more recent
> bison), but at that point libpq was already finished. This still
> resulted in more or less the same kind of errors.

Are you sure that each thread is accessing only its own PGconn object?

Other than that, not sure what to suggest.  I get the impression that
something is clobbering memory with abandon.  Do you have any
Purify-like tools to look for memory stomp problems?

			regards, tom lane

In response to

Responses

pgsql-interfaces by date

Next:From: Frank van VugtDate: 2003-08-05 07:13:40
Subject: Fwd: Re: Multi-threaded user app segfaults when using libpq with separate connections
Previous:From: Frank van VugtDate: 2003-08-04 22:34:20
Subject: Re: Multi-threaded user app segfaults when using libpq with separate connections

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