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 | bff7bc6cb785191041aa7530febdbb5cfe6eaf06 (patch) | |
tree | e68b6babd8f6e3e9d0d1fb59adabb98b73e1d757 /src/backend/access/gist/gistxlog.c | |
parent | b53d104ae3b9cb0acfc6bb429261005bd07d3b3e (diff) | |
download | postgresql-bff7bc6cb785191041aa7530febdbb5cfe6eaf06.tar.gz postgresql-bff7bc6cb785191041aa7530febdbb5cfe6eaf06.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/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions