| From: | Walker <failaway(at)qq(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 回复: unrecognized configuration parameter "plpgsql.check_asserts" |
| Date: | 2021-03-12 12:38:51 |
| Message-ID: | tencent_91959498B856E88485A68E6C09F57FAFE707@qq.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
thanks Julien & Pavel
it's crystal clear now. thanks again for your kindly help
thanks
walker
------------------ Original ------------------
From: "Julien Rouhaud" <rjuju123(at)gmail(dot)com>;
Date: Fri, Mar 12, 2021 08:27 PM
To: "Walker"<failaway(at)qq(dot)com>;
Cc: "Pavel Stehule"<pavel(dot)stehule(at)gmail(dot)com>;"pgsql-hackers"<pgsql-hackers(at)lists(dot)postgresql(dot)org>;
Subject: Re: 回复: unrecognized configuration parameter "plpgsql.check_asserts"
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_asserts configuration option, whether the server were compiled
with or without --enable-cassert.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2021-03-12 12:44:02 | Re: MultiXact\SLRU buffers configuration |
| Previous Message | Amit Kapila | 2021-03-12 12:35:30 | Re: Do we support upgrade of logical replication? |