Re: Assertions in PL/PgSQL
От | Jaime Casanova |
---|---|
Тема | Re: Assertions in PL/PgSQL |
Дата | |
Msg-id | CAJKUy5i2DFDYmQ2MmVnyb4ZrPJOLk1WBsnOox3KKcbGi+d4H-w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Assertions in PL/PgSQL (Marko Tiikkaja <marko@joh.to>) |
Ответы |
Re: Assertions in PL/PgSQL
|
Список | pgsql-hackers |
<p>On Sat, Sep 14, 2013 at 1:52 PM, Marko Tiikkaja <<a href="mailto:marko@joh.to">marko@joh.to</a>> wrote:<br /> >On 14/09/2013 20:47, I wrote:<br /> >><br /> >> These are<br /> >> similar to the Assert() backendmacro: they can be disabled during<br /> >> compile time, but when enabled, abort execution if the passed expression<br/> >> is not true.<br /> ><p>Hi,<p>That's very good, thanks.<p>><br /> > And by "compile time"here, I mean at the time when the PL/PgSQL function is<br /> > compiled, not the postgres server binary.<br /> ><p>and"compile time" means when the function is created or replaced? or the first time is used?<p>if the second. Whynot have a plpgsql.enable_assert variable?<br /> A directive you can use per function <p>then i can keep the ASSERT andactivate them by replacing the function<p>-- <br /> Jaime Casanova <a href="http://www.2ndQuadrant.com">www.2ndQuadrant.com</a><br/> Professional PostgreSQL: Soporte 24x7 y capacitación<br />Phone: +593 4 5107566 Cell: +593 987171157
В списке pgsql-hackers по дате отправления: