thanks Julien & Pavel
it's crystal clear now. thanks again for your kindly help
thanks
walker
-- Original --
From:
"Julien Rouhaud"
On Fri, Mar 12, 2021 at 08:12:53PM +0800, Walker wrote:
> 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, those are two different things. plpgsql ASSERT are only controlled by
plpgsql.check_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 thou
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&q
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
pl
;
EORROR: unrecognized configuration parameter "plpgsql.check_asserts"
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-l
