| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Assertions in PL/PgSQL |
| Date: | 2013-11-27 04:41:40 |
| Message-ID: | 1385527300.28256.15.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2013-11-27 05:05:15 | Re: New option for pg_basebackup, to specify a different directory for pg_xlog |
| Previous Message | Rajeev rastogi | 2013-11-27 04:29:50 | Re: COPY table FROM STDIN doesn't show count tag |