Re: Ideas for easier debugging of backend problems - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Ideas for easier debugging of backend problems
Date
Msg-id 20051027172057.GL4259@svana.org
Whole thread Raw
In response to Re: Ideas for easier debugging of backend problems  (Douglas McNaught <doug@mcnaught.org>)
Responses Re: Ideas for easier debugging of backend problems
List pgsql-hackers
On Thu, Oct 27, 2005 at 01:13:37PM -0400, Douglas McNaught wrote:
> "Jim C. Nasby" <jnasby@pervasive.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...

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Test settings in postgresql.conf.sample in beta4
Next
From: Michael Fuhr
Date:
Subject: Re: Test settings in postgresql.conf.sample in beta4