From: andrew klassen <aptklassen@yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: postmaster process and multithreading
Date: Wed, 28 Nov 2007 16:11:56 -0800 (PST)
Message-ID: <725224.69490.qm@web37302.mail.mud.yahoo.com> (raw)
I am only using a "C" based client with libpq. But, I did not explicitly turn
anything off like perl or tcl. Are these off by default?
Is there some way to check in the gdb or compile log?
thanks.
----- Original Message ----
From: Tom Lane <tgl@sss.pgh.pa.us>
To: andrew klassen <aptklassen@yahoo.com>
Cc: pgsql-interfaces <pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 28, 2007 5:08:12 PM
Subject: Re: [INTERFACES] postmaster process and multithreading
andrew klassen <aptklassen@yahoo.com> writes:
> The reason I am asking is because sometimes the postmaster
> will create a core dump and it will show two threads but the
> backtrace on both threads does not show any helpful information.
Are you using plperl or pltcl? The backend shouldn't go multithreaded,
but we've seen problems with those interpreters causing it to happen.
(I suppose other language interpreters like python might be risks as
well, but those two are the only ones trouble has been reported with.)
regards, tom lane
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
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: aptklassen@yahoo.com, tgl@sss.pgh.pa.us
Subject: Re: postmaster process and multithreading
In-Reply-To: <725224.69490.qm@web37302.mail.mud.yahoo.com>
* 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