| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Tiikkaja <marko(at)joh(dot)to>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: plpgsql - Assert statement |
| Date: | 2014-11-26 07:55:30 |
| Message-ID: | CAFj8pRCToThR+zDT7Km_EdHWFkjeELNxXy8w+Jbg1j85=xrpOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all
so one problem is closed, and we can start speaking about ASSERT statement.
I propose a (old) syntax
ASSERT expr [, message]
possible questions:
* should be assertions globally enabled/disabled? - I have no personal
preference in this question.
* can be ASSERT exception handled ? - I prefer this be unhandled exception
- like query_canceled because It should not be masked by plpgsql EXCEPTION
WHEN OTHERS ...
Ideas, notices?
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jakob Egger | 2014-11-26 08:01:42 | Re: [pgsql-packagers] Palle Girgensohn's ICU patch |
| Previous Message | Palle Girgensohn | 2014-11-26 07:41:49 | Re: [pgsql-packagers] Palle Girgensohn's ICU patch |