Re: 回复： unrecognized configuration parameter "plpgsql.check_asserts"

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
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"
Date: 2021-03-12 12:27:51
Message-ID: 20210312122751.txjwuraxfv6vatr2@nol
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-03-12 12:35:30 Re: Do we support upgrade of logical replication?
Previous Message Pavel Stehule 2021-03-12 12:25:59 Re: unrecognized configuration parameter "plpgsql.check_asserts"