From: | Alexey Klyukin <alexk(at)commandprompt(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | errcontext support in PL/Perl |
Date: | 2009-07-21 13:47:47 |
Message-ID: | 8EED7D1A-9E12-4081-A0A7-B3EC7011854B@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
While trying to build a custom error reporting function for one of our
clients we came across the fact that PL/Perl doesn't set errcontext
that we relied on to get the traceback of running functions. Exactly
the same problem with PL/Python was fixed recently by Peter Eisentraut
(http://archives.postgresql.org/pgsql-committers/2009-07/msg00168.php)
Attached is a patch (HEAD) that sets errcontext with PL/Perl function
name, making a distinction between compilation and execution stages,
fixes error messages where function name was already included in the
message itself and updates regression tests. I'll appreciate any
suggestions on how to improve it.
Attachment | Content-Type | Size |
---|---|---|
plperl_error_callback.diff | application/octet-stream | 14.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-07-21 13:50:58 | Re: [PATCH] user mapping extension to pg_ident.conf |
Previous Message | Tom Lane | 2009-07-21 13:46:25 | Re: pg_restore --clean vs. large object |