Re: Ideas for easier debugging of backend problems

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Douglas McNaught <doug(at)mcnaught(dot)org>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, 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:20:57
Message-ID: 20051027172057.GL4259@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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...

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Fuhr 2005-10-27 17:24:25 Re: Test settings in postgresql.conf.sample in beta4
Previous Message Tom Lane 2005-10-27 17:16:40 Re: Test settings in postgresql.conf.sample in beta4