Re: Assertions in PL/PgSQL - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Assertions in PL/PgSQL
Date
Msg-id 1385527300.28256.15.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Assertions in PL/PgSQL  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Assertions in PL/PgSQL
List pgsql-hackers
On Tue, 2013-11-19 at 10:40 -0500, Robert Haas wrote:
> I think the goal was to get to RAISE ASSERT
> WHEN ...; then, if assertions are off, you do nothing; if they're on,
> you error.  IF condition THEN RAISE..." isn't a suitable surrogate in
> that case because you incur the overhead of testing the condition
> regardless.

So if I do RAISE ASSERT WHEN condition and assertions are off, then
condition wouldn't even be evaluated?  But what about RAISE NOTICE WHEN,
when log_min_messages is error?  What about the side effects of the
format string?  This is all just getting too weird.

I don't see anything wrong with considering a separate ASSERT command
with its own semantics, like in many other programming languages.





pgsql-hackers by date:

Previous
From: Rajeev rastogi
Date:
Subject: Re: COPY table FROM STDIN doesn't show count tag
Next
From: Fujii Masao
Date:
Subject: Re: New option for pg_basebackup, to specify a different directory for pg_xlog