Skip site navigation (1) Skip section navigation (2)

Re: proposal: use errcontext for custom exception too

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 13:31:55
Message-ID: CA+TgmobpE0ARv9ngZymQ+tnn6Gf3cvNKj8p32FA+X7LhLc4pMA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Nov 25, 2011 at 1:14 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> A some option via #option or GUC has sense for lower levels like
> NOTICE or WARNING.

I think what we discussed before was adding some bit of optional
syntax to RAISE that would indicate that the user wants CONTEXT
suppressed.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Dean RasheedDate: 2011-11-25 16:16:29
Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Previous:From: Robert HaasDate: 2011-11-25 13:19:08
Subject: Re: Storing hot members of PGPROC out of the band

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group