Edson Richter <edsonrichter@xxxxxxxxxxx> 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general