| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: enhanced get diagnostics statement |
| Date: | 2011-05-21 21:57:47 |
| Message-ID: | 1306014993-sup-3896@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Pavel Stehule's message of sáb may 21 16:05:01 -0400 2011:
> A implementation of ERROR_CONTEXT is not without impact on
> performance, because context should be collected when exception is
> caught. One solution is removing a ERROR_CONTEXT from proposal. Second
> solution can be a design of enhanced syntax for exception trap like
> (it means - collect CONTEXT when exception is handled)
I don't understand why we should worry about this. I mean, if you don't
catch the error, you have to form errcontext anyway. Why is it a
problem to generate it when the exception is caught?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-05-21 23:51:18 | Re: eviscerating the parser |
| Previous Message | Peter Eisentraut | 2011-05-21 21:47:56 | about EDITOR_LINENUMBER_SWITCH |