| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: Assertions in PL/PgSQL |
| Date: | 2013-09-15 22:51:49 |
| Message-ID: | CAJKUy5h_fGd09Uu7x2N951f-TV0DBce0E1AFgbH8BwoRz-EG-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
El 15/09/2013 17:13, "Marko Tiikkaja" <marko(at)joh(dot)to> escribió:
>
> On 2013-09-15 23:23, Jaime Casanova wrote:
>>
>> If using ASSERT as keyword is not acceptable, not that i agree but in
case.
>> What about using RAISE EXCEPTION WHEN (condition)
>
>
> I think it would be extremely surprising if a command like that got
optimized away based on a GUC, so I don't think that would be a good idea.
>
>
Ah! good point, didn't think on that
--
Jaime Casanova
2ndQuadrant: Your PostgreSQL partner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2013-09-15 23:49:26 | Re: record identical operator |
| Previous Message | Marko Tiikkaja | 2013-09-15 22:13:26 | Re: Assertions in PL/PgSQL |