Re: Proposal "stack trace" like debugging option in PostgreSQL - Mailing list pgsql-general

From Tom Lane
Subject Re: Proposal "stack trace" like debugging option in PostgreSQL
Date
Msg-id 20401.1469980571@sss.pgh.pa.us
Whole thread Raw
In response to Proposal "stack trace" like debugging option in PostgreSQL  (Edson Richter <edsonrichter@hotmail.com>)
Responses Re: Proposal "stack trace" like debugging option in PostgreSQL
List pgsql-general
Edson Richter <edsonrichter@hotmail.com> writes:
> But in production this is not possible, and I would to propose a feature
> that has less impact over production then a debug extension: a
> stacktrace of calls.

> Simular to Java stack traces, but disabled by default. When enabled, In
> case of an event like "duplicate key" (or a function raise exception) or
> other similar problems that wont allow the database to execute the SQL
> command,the strack trace will bring the complete list of function call.

Uh, doesn't the CONTEXT field of error messages give you that already?

            regards, tom lane


pgsql-general by date:

Previous
From: Jason Dusek
Date:
Subject: Re: Uber migrated from Postgres to MySQL
Next
From: Edson Richter
Date:
Subject: Re: Proposal "stack trace" like debugging option in PostgreSQL