Re: Call stacks and RAISE INFO

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Call stacks and RAISE INFO
Date: 2011-10-15 10:55:10
Message-ID: CAFj8pRBc_qAdAhPdekGAFiDWVJJC9jU=cOHDHStm97f_Kd1WpA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2011/10/15 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Sat, Oct 15, 2011 at 12:24 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> I have no problem with this.  A context can be false for info and true
>> for other in default. Please, use a different identifier than
>> "context", that can be use for reading context in future - maybe
>> "attach_context" or some similar.
>
> error_context?

what about show_context, hide_context, hold_context, use_context ??

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian Pflug 2011-10-15 11:41:21 Re: LIMITing number of results in a VIEW with global variables
Previous Message Robert Haas 2011-10-15 10:51:35 Re: [HACKERS] register creation date of table