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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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. 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: Thu, 27 Oct 2005 19:20:57 +0200
  • Message-id: <20051027172057(dot)GL4259(at)svana(dot)org>

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.

Attachment: pgpMpTgD2QNjm.pgp
Description: PGP signature



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group