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

In response to

• proposal: use errcontext for custom exception too at 2011-11-24 17:30:03 from Pavel Stehule

Responses

• Re: proposal: use errcontext for custom exception too at 2011-11-25 06:14:56 from Pavel Stehule
• Re: proposal: use errcontext for custom exception too at 2011-11-25 16:53:21 from Tom Lane

pgsql-hackers by date

Next:	From: Andrew Dunstan	Date: 2011-11-25 03:52:37
	Subject: Re: [PATCH] PostgreSQL fails to build with 32bit MinGW-w64
Previous:	From: Robert Haas	Date: 2011-11-25 01:56:07
	Subject: Re: logging in high performance systems.