| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Jaime Casanova <jaime(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com> |
| Subject: | Re: Assertions in PL/PgSQL |
| Date: | 2013-09-23 09:00:50 |
| Message-ID: | 52400342.206@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/23/13 10:50 AM, I wrote:
> On 9/23/13 6:40 AM, Pavel Stehule wrote:
>> After days I am thinking so it can be a good solution
>>
>> syntax - enhanced current RAISE
>>
>> RAISE ASSERT WHEN boolean expression
>>
>> RAISE ASSERT 'some message' WHEN expression
>
> It looks like I'm losing this battle, but this syntax isn't too bad.
>
>> and we can have a GUC that controls asserts per database - possibly
>> overwritten by plpgsql option - similar to current plpgsql options
>>
>> assert_level = [*ignore*, notice, warning, error]
>
> This sounds like a decent enhancement.
Oh, it would be nice to have the option here to say "assertions can't be
caught by exception handlers", but I don't know how that mechanism works
so I'm not sure it's possible. I'll have to look into that.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Khandekar | 2013-09-23 09:01:25 | Re: Assertions in PL/PgSQL |
| Previous Message | Pavel Stehule | 2013-09-23 08:57:01 | Re: Assertions in PL/PgSQL |