From: Tom Lane <tgl@sss.pgh.pa.us>
To: Frank van Vugt <ftm.van.vugt@foxi.nl>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Multi-threaded user app segfaults when using libpq with separate connections
Date: Mon, 04 Aug 2003 18:41:02 -0400
Message-ID: <13531.1060036862@sss.pgh.pa.us> (raw)
In-Reply-To: <200308050034.20405.ftm.van.vugt@foxi.nl>
References: <200308041729.13212.ftm.van.vugt@foxi.nl>
<2778.1060012055@sss.pgh.pa.us>
<200308050034.20405.ftm.van.vugt@foxi.nl>
Frank van Vugt <ftm.van.vugt@foxi.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, ftm.van.vugt@foxi.nl
Subject: Re: Multi-threaded user app segfaults when using libpq with separate connections
In-Reply-To: <13531.1060036862@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox