On 1/21/15 3:10 PM, Pavel Stehule wrote:
is there some agreement on this behave of ASSERT statement? I would to assign last patch to next commitfest. Possible changes: * I would to simplify a behave of evaluating of message expression - probably I disallow NULL there.
Well, the only thing I could see you doing there is throwing a different error if the hint is null. I don't see that as an improvement. I'd just leave it as-is.
* GUC enable_asserts will be supported
That would be good. Would that allow for enabling/disabling on a per-function basis too?
* a assert exception should not be handled by PLpgSQL handler -- like CANCEL exception
+1 -- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
