mirror of
https://github.com/postgres/postgres.git
synced 2026-02-25 19:02:00 -05:00
d8e1de899c
Places that are testing for *printf failure ought to include the format string in their error reports, since bad-format-string is one of the more likely causes of such failure. This both makes it easier to find and repair the mistake, and provides at least some useful info to the user who stumbles across such a problem. Also, tighten snprintf.c to report EINVAL for an invalid flag or final character in a format %-spec (including the case where the %-spec is missing a final character altogether). This seems like better project policy, and it also allows removing an instruction or two from the hot code path. Back-patch the error reporting change in pvsnprintf, since it should be harmless and may be helpful; but not the snprintf.c change. Per discussion of bug #15511 from Ertuğrul Kahveci, which reported an invalid translated format string. These changes don't fix that error, but they should improve matters next time we make such a mistake. Discussion: https://postgr.es/m/15511-1d8b6a0bc874112f@postgresql.org |
||
|---|---|---|
| .. | ||
| unicode | ||
| base64.c | ||
| config_info.c | ||
| controldata_utils.c | ||
| exec.c | ||
| fe_memutils.c | ||
| file_perm.c | ||
| file_utils.c | ||
| ip.c | ||
| keywords.c | ||
| Makefile | ||
| md5.c | ||
| pg_lzcompress.c | ||
| pgfnames.c | ||
| psprintf.c | ||
| relpath.c | ||
| restricted_token.c | ||
| rmtree.c | ||
| saslprep.c | ||
| scram-common.c | ||
| sha2.c | ||
| sha2_openssl.c | ||
| string.c | ||
| unicode_norm.c | ||
| username.c | ||
| wait_error.c | ||