Re: proposal: use errcontext for custom exception too

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: use errcontext for custom exception too
Date: 2011-11-25 16:53:21
Message-ID: 11350.1322240001@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 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.

Note also that the current behavior *is* what people want; at least,
we have seen no field complaints about the lack of first-level CONTEXT
for RAISE notices, and plenty of complaints from people who think
there's still too much cruft automatically attached to RAISE output.
If anything, what's been requested is a way to suppress even more
context, not a policy decision to force more of it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2011-11-25 17:49:08 Re: proposal: use errcontext for custom exception too
Previous Message Tom Lane 2011-11-25 16:48:09 Re: proposal : backend startup hook / after logon trigger