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

Re: postmaster process and multithreading

From: andrew klassen <aptklassen(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: postmaster process and multithreading
Date: 2007-11-29 00:11:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
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? 


----- Original Message ----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: andrew klassen <aptklassen(at)yahoo(dot)com>
Cc: pgsql-interfaces <pgsql-interfaces(at)postgresql(dot)org>
Sent: Wednesday, November 28, 2007 5:08:12 PM
Subject: Re: [INTERFACES] postmaster process and multithreading

andrew klassen <aptklassen(at)yahoo(dot)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.

pgsql-interfaces by date

Next:From: Adam RadłowskiDate: 2007-12-06 21:02:49
Subject: Re: libpq crashing under Vista
Previous:From: Tom LaneDate: 2007-11-28 23:08:12
Subject: Re: postmaster process and multithreading

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