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

From Peter Eisentraut
Subject Re: Ideas for easier debugging of backend problems
Date
Msg-id 200511011233.39589.peter_e@gmx.net
Whole thread Raw
In response to Ideas for easier debugging of backend problems  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Ideas for easier debugging of backend problems
Re: Ideas for easier debugging of backend problems
Re: Ideas for easier debugging of backend problems
List pgsql-hackers
Martijn van Oosterhout wrote:
> 3. Add either a GUC or a command line switch or PGOPTION switch  to
> automatically invoke and attach gdb on certain types of error.
> Obviously you can only do this where stdin, stdout and stderr have
> not been redirected.

Samba has a configuration parameter that allows you to set an arbitrary 
command as a "panic action" script.  This can then be used to gather 
debugging information or prepare a bug report (see other thread).  This 
also has the added flexibility that binary packagers can add extra 
information specific to their environment.  It may be worthwhile to 
research whether we could do something similar.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: strk@refractions.net
Date:
Subject: FreeBSD broke with autoconf-based build
Next
From: Salman Razzaq
Date:
Subject: Adding a column in pg_proc for storing default values of arguments