| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 15:46:23 |
| Message-ID: | CAFj8pRDrNUXwHVe1pfzmOO1SQK0AJ_wBsGzERb9fw3JkdAfrsA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2014-11-26 13:31 GMT+01:00 Marko Tiikkaja <marko(at)joh(dot)to>:
> On 11/26/14 8:55 AM, Pavel Stehule wrote:
>
>> * should be assertions globally enabled/disabled? - I have no personal
>> preference in this question.
>>
>
> I think so. The way I would use this function is to put expensive checks
> into strategic locations which would only run when developing locally (and
> additionally perhaps in one of the test environments.) And in that case
> I'd like to globally disable them for the live environment.
>
ok
>
> * 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 ...
>>
>
> I don't care much either way, as long as we get good information about
> what went wrong. A stack trace and hopefully something like
> print_strict_params for parameters to the "expr".
>
There is more ways, I can live with both
Pavel
>
>
> .marko
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sawada Masahiko | 2014-11-26 15:55:48 | Re: Proposal : REINDEX SCHEMA |
| Previous Message | Andrew Gierth | 2014-11-26 15:41:18 | Re: Follow up to irc on CREATE INDEX vs. maintenance_work_mem on 9.3 |