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.steh...@gmail.com>; ????????: 2021??3??12??(??????) ????7:11 ??????: "Walker"<faila...@qq.com>; ????: "pgsql-hackers"<pgsql-hackers@lists.postgresql.org>; ????: Re: unrecognized configuration parameter "plpgsql.check_asserts" p?? 12. 3. 2021 v 11:54 odes??latel Walker <faila...@qq.com> 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: 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