Re: Ideas for easier debugging of backend problems

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Douglas McNaught <doug(at)mcnaught(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Ideas for easier debugging of backend problems
Date: 2005-10-27 17:38:34
Message-ID: 20051027173834.GH63747@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 27, 2005 at 07:20:57PM +0200, Martijn van Oosterhout wrote:
> On Thu, Oct 27, 2005 at 01:13:37PM -0400, Douglas McNaught wrote:
> > "Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> >
> > > It would also be useful to be able to force the backend to
> > > dump core so you can see if it's actually working (granted, I know you
> > > can end up hitting the ulimit depending on how much memory is being
> > > consumed). Maybe there is a way to do this already and I just don't know
> > > it...
> >
> > SIGABRT?
>
> Still doesn't do anything if core dumps are disabled. The point is to
> enable the user to enable core dumps from the frontend, rather than
> having to fiddle the backend environment directly...

Actually, SIGABRT is what I was looking for... I wanted a way to force a
backend to dump core so I could see if a corefile would actually be
generated.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2005-10-27 18:03:40 Re: Test settings in postgresql.conf.sample in beta4
Previous Message Michael Fuhr 2005-10-27 17:24:25 Re: Test settings in postgresql.conf.sample in beta4