diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-09-15 17:17:53 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-09-15 17:17:53 -0400 |
commit | cf2c7a736e4939ff0d6cf2acd29b17eea3bca7c2 (patch) | |
tree | f776d138d102dbfed014ed4f3770581a48a46e6f /src/backend/commands/dbcommands.c | |
parent | 3a06a79cd137d294bc82d931769d778c8c9aec91 (diff) | |
download | postgresql-cf2c7a736e4939ff0d6cf2acd29b17eea3bca7c2.tar.gz postgresql-cf2c7a736e4939ff0d6cf2acd29b17eea3bca7c2.zip |
Detect format-string mistakes in the libpq_pipeline test module.
I happened to notice that libpq_pipeline's private implementation
of pg_fatal lacked any pg_attribute_printf decoration. Indeed,
adding that turned up a mistake! We'd likely never have noticed
because the error exits in this code are unlikely to get hit,
but still, it's a bug.
We're so used to having the compiler check this stuff for us that
a printf-like function without pg_attribute_printf is a land mine.
I wonder if there is a way to detect such omissions.
Back-patch to v14 where this code came in.
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions