2014-11-26 13:31 GMT+01:00 Marko Tiikkaja <ma...@joh.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 >
