| 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-22 17:56:20 |
| Message-ID: | CAFj8pRB6Ge-5TTvZb_7K2ec1Sd_m4vK_7cWZy4M1pPfyXA=7wQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2013/8/22 Marko Tiikkaja <marko(at)joh(dot)to>
> On 8/22/13 9:08 AM, Pavel Stehule wrote:
>
>> Probably we can introduce a new level of verbosity, but I am thinking so
>> this behave is reasonable. Everybody who use a VERBOSE level expect lot of
>> balast and it show expected info (context of error)
>>
>> Can be this design good enough for you?
>>
>
> 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.
>
>
word "DEBUG" is not good - it is used for Postgres debugging as log level
Pavel
>
> Regards,
> Marko Tiikkaja
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei KaiGai | 2013-08-22 19:53:37 | Does larger i/o size make sense? |
| Previous Message | Tom Lane | 2013-08-22 17:47:49 | Re: Allow child table to be missing nullable column from parent. |