回复： unrecognized configuration parameter "plpgsql.check_asserts"

Hi, Pavel

Thanks for your comments. 

To get rid of --enable-cassert while configuring, debug_assertions is shown as off. In this case, ASSERT statement also can't be used, right?

when enable --enable-cassert, can we use plpgsql.check_asserts to control ASSERT statement, and how? 

thanks
walker

------------------ 原始邮件 ------------------
发件人: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com&gt;;
发送时间:&nbsp;2021年3月12日(星期五) 晚上7:11
收件人:&nbsp;"Walker"<failaway(at)qq(dot)com&gt;;
抄送:&nbsp;"pgsql-hackers"<pgsql-hackers(at)lists(dot)postgresql(dot)org&gt;;
主题:&nbsp;Re: unrecognized configuration parameter "plpgsql.check_asserts"

pá 12. 3. 2021 v&nbsp;11:54 odesílatel Walker <failaway(at)qq(dot)com&gt; napsal:

Hi, hackers

Due to configure with parameter --enable-cassert, the debug_assertions is on by default, as follows:
postgres=# show debug_assertions;
debug_assertions
-------------------
on

Because of pgbench performance testing, I need to disable the assert function. Following the doc below, I tried to set plpgsql.check_asserts to off to disable assert function.
https://www.postgresql.org/docs/13/plpgsql-errors-and-messages.html

However, it prompts the following error, not sure if I missed something, any thoughts about it?
postgres=# alter system set plpgsql.check_asserts = off;
EORROR:&nbsp;unrecognized configuration parameter "plpgsql.check_asserts"

you cannot disable debug_assertions. It is possible just by configure, and make

plpgsql.check_asserts controls evaluation of plpgsql statement ASSERT

Pavel

env:
PG: 13.2
OS: redhat 7.4 3.10.0-693.17.1.e17.x86_64
configure parameter: --enable-coverage --enable-tap-tests --enable-cassert --enable-debug --enable-nls --with-perl --with-python --with-tcl --with-openssl --with-ldap --with-libxml --with-libxslt --with-uuid=e2fs --with-segsize=10 --with-wal-blocksize=16 --with-llvm LLVM_CONFIG=xxx CLANG=xxx

thanks
walker