Re: elog a stack trace

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: MauMau <maumau307(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: elog a stack trace
Date: 2014-05-06 16:32:08
Message-ID: 20140506163208.GU6018@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

MauMau wrote:

> On Windows, you can use Stackwalk() or Stackwalk64() Win32 API.
> Several years ago, for some software, I implemented a feature that
> outputs the stack trace of a crashing process to its server log
> file.
>
> It would be very nice if PostgreSQL outputs the stack trace of a
> crashing postgres process in the server log. That eliminates the
> need for users in many cases to send the huge core files to the
> support staff or to use the debugger to get the stack trace. I've
> recently heard that MySQL has this feature.

+1, assuming it can be made to work reliably and does not cause a larger
reliability problem. I see the GNU extension to get backtraces, for
instance, tries to malloc stuff in order to get a human-readable trace,
which might not be all that great.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-05-06 16:36:08 Re: doPickSplit stack buffer overflow in XLogInsert?
Previous Message Alvaro Herrera 2014-05-06 16:29:57 Re: Sending out a request for more buildfarm animals?