| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: use errcontext for custom exception too |
| Date: | 2011-11-25 02:19:49 |
| Message-ID: | CA+TgmoaxxWKCGNWWDTA_t+fWP8+A391oz-4kBUNGJZJrvcu4ZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 24, 2011 at 12:30 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> There are small issue in PL/pgSQL and custom exceptions. Custom
> exception doesn't set a CONTEXT field. I propose change this behave
> for WARNING or EXCEPTION level. The goal is same behave for custom
> exception and builtin exception and it can help to identify a RAISE
> statement that is responsible to exception.
That seems completely arbitrary. I think we discussed before
providing an option to allow the user to control this, which seems
better than implementing some hardcoded rule that may or may not be
what a given user wants.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-11-25 03:52:37 | Re: [PATCH] PostgreSQL fails to build with 32bit MinGW-w64 |
| Previous Message | Robert Haas | 2011-11-25 01:56:07 | Re: logging in high performance systems. |