aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/dbcommands.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-09-15 17:17:53 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2022-09-15 17:17:53 -0400
commit4e2a88905d7c05066a3caddc1f6ee76864e24c38 (patch)
treeb78f31078348af8c63ba161bb4b5a556925d334e /src/backend/commands/dbcommands.c
parentbfa58a679a577bffa58cd122b77483f508ed5933 (diff)
downloadpostgresql-4e2a88905d7c05066a3caddc1f6ee76864e24c38.tar.gz
postgresql-4e2a88905d7c05066a3caddc1f6ee76864e24c38.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