pgsql: Avoid compiler warning in non-assert builds

From: Amit Langote <amitlan(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Avoid compiler warning in non-assert builds
Date: 2023-10-26 08:33:26
Message-ID: E1qvvny-002Oav-4X@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Avoid compiler warning in non-assert builds

After 01575ad788e3, expand_single_inheritance_child()'s parentOID
variable is read only in an Assert, provoking a compiler warning in
non-assert builds. Fix that by marking the variable with
PG_USED_FOR_ASSERTS_ONLY.

Per report and suggestion from David Rowley

Discussion: https://postgr.es/m/CAApHDvpjA_8Wxu4DCTRVAvPxC9atwMe6N%2ByvrcGsgb7mrfdpJA%40mail.gmail.com

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2bf99b48ded8288fa1c5f53a0c3581059a112d0c

Modified Files
--------------
src/backend/optimizer/util/inherit.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Langote 2023-10-26 08:33:52 pgsql: Avoid compiler warning in non-assert builds
Previous Message Amit Langote 2023-10-26 08:08:01 Re: pgsql: Prevent duplicate RTEPermissionInfo for plain-inheritance parent