aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorNeil Conway <neilc@samurai.com>2005-04-30 08:36:18 +0000
committerNeil Conway <neilc@samurai.com>2005-04-30 08:36:18 +0000
commita935e36ae9674f63887cdb7d94e1c31cb08e08c4 (patch)
tree3e3f32e9004f690770a261adbca69638f3a2abe1 /src/backend/access/gist
parent15ea6d5a2fdc57ef14ebf2c06f4f7392b6599899 (diff)
downloadpostgresql-a935e36ae9674f63887cdb7d94e1c31cb08e08c4.tar.gz
postgresql-a935e36ae9674f63887cdb7d94e1c31cb08e08c4.zip
GCC 4.0 includes a new warning option, -Wformat-literal, that emits
a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Most of these are harmless (e.g. the ruleutils stuff), but there is at least one actual bug here: if you create a trigger named "%sfoo", pg_dump will read uninitialized memory and fail to dump the trigger correctly.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions