Re: unrecognized configuration parameter "plpgsql.check_asserts"

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Walker <failaway(at)qq(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: unrecognized configuration parameter "plpgsql.check_asserts"
Date: 2021-03-12 12:25:59
Message-ID: CAFj8pRAQHqP9=uZ36u0rM8Js0cCz7K8ZcbG0PG2HnJQbuPQKFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pá 12. 3. 2021 v 13:13 odesílatel Walker <failaway(at)qq(dot)com> napsal:

> 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?
>

no - debug assertions and plpgsql assertions are two absolutely independent
features.

--enable-cessart enables C assertions, and then needs postgres's source
code compilation. It is designed and used by Postgres's core developers.

plpgsql's ASSERT is user space feature, and can be enabled or disabled how
it is necessary by plpgsql.check_assert.

> 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>;
> *发送时间:* 2021年3月12日(星期五) 晚上7:11
> *收件人:* "Walker"<failaway(at)qq(dot)com>;
> *抄送:* "pgsql-hackers"<pgsql-hackers(at)lists(dot)postgresql(dot)org>;
> *主题:* Re: unrecognized configuration parameter "plpgsql.check_asserts"
>
>
>
> pá 12. 3. 2021 v 11:54 odesílatel Walker <failaway(at)qq(dot)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
>>
>>
>>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2021-03-12 12:27:51 Re: 回复: unrecognized configuration parameter "plpgsql.check_asserts"
Previous Message Walker 2021-03-12 12:12:53 回复: unrecognized configuration parameter "plpgsql.check_asserts"