pgsql: Clean up minor inconsistencies in pg_attribute_printf() usage.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Clean up minor inconsistencies in pg_attribute_printf() usage.
Date: 2022-09-16 15:11:00
Message-ID: E1oZCzc-000cPM-3w@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Clean up minor inconsistencies in pg_attribute_printf() usage.

For some reason we'd never decorated pg_v*printf() with
pg_attribute_printf() annotations. There is a convention for
how to label va_list-using printf functions (write zero for the
second argument), and we use that liberally elsewhere in the
code, but these core functions lacked it. It's not clear how
much useful checking the compiler can do for calls of these,
but we might as well add the annotations.

Also, sync win32security.c's log_error() with our normal convention
that pg_attribute_printf must be attached to a function's declaration
not definition. Apparently this file is only compiled with compilers
that aren't picky about that, but still it'd be better to be
consistent.

No back-patch since there's little reason to think we would catch
anything.

Discussion: https://postgr.es/m/3492412.1663283395@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/eacbe94ab1f46d94a8532f9b9ac83ccd98cc1287

Modified Files
--------------
src/include/port.h | 8 ++++----
src/port/win32security.c | 6 +++---
2 files changed, 7 insertions(+), 7 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2022-09-16 15:58:08 pgsql: aix: xlc: Use -Wl,-b,expfull for old compiler versions
Previous Message Peter Eisentraut 2022-09-16 14:51:05 pgsql: Message wording improvements