Re: PL/pgSQL, RAISE and error context

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Marko Tiikkaja <marko(at)joh(dot)to>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/pgSQL, RAISE and error context
Date: 2013-08-23 11:42:44
Message-ID: CAFj8pRB121jGSdz-BzSiwFcLbATHxb5j7jot4FediQ+8QyRPuA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013/8/23 Marko Tiikkaja <marko(at)joh(dot)to>

> On 8/23/13 8:38 AM, Pavel Stehule wrote:
>
> 2013/8/22 Marko Tiikkaja <marko(at)joh(dot)to>
>>
>>> I like the idea, but I think this should be a new verbosity level. With
>>> this patch you would have to go full VERBOSE just to debug PL/pgSQL code
>>> with NOTICEs and DEBUGs in it, and that output then becomes harder to
>>> parse
>>> with the useless C-code information.
>>>
>>>
>> do you prepare patch ?
>>
>
> I should have the time to produce one for the September commitfest, but if
> you (or anyone else) want to work on this, I won't object.
>
> My opinion at this very moment is that we should leave the the DEFAULT
> verbosity alone and add a new one (call it COMPACT or such) with the
> suppressed context for non-ERRORs.
>

The name is not important. What I would, for DEFAULT verbosity, to see a
context when RAISE EXCEPTION is used. It is a bug now, I think

Regards

Pavel

>
>
> Regards,
> Marko Tiikkaja
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2013-08-23 12:31:05 Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Previous Message Fabien COELHO 2013-08-23 09:11:06 Re: Does larger i/o size make sense?