pgsql: Fix silly initializations (cosmetic only). - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix silly initializations (cosmetic only).
Date
Msg-id E1iUzEF-0003aN-F8@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix silly initializations (cosmetic only).

Initializing a pointer to "false" isn't per project style,
and reportedly some compilers warn about it (though I've
not seen any such warnings in the buildfarm).

Seems to have come in with commit ff11e7f4b, so back-patch
to v12 where that was added.

Didier Gautheron

Discussion: https://postgr.es/m/CAJRYxu+XQuM0qnSqt1Ujztu6fBPzMMAT3VEn6W32rgKG6A2Fsw@mail.gmail.com

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/99cc47b1d85aabc4a80910c839073f83a4fb163b

Modified Files
--------------
src/backend/commands/trigger.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Avoid using SplitIdentifierString to parse ListenAddresses, too.
Next
From: Tom Lane
Date:
Subject: pgsql: Add missing check_collation_set call to bpcharne().