aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-05-09 02:16:00 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-05-09 02:16:00 +0000
commited437e2b27c48219a78f3504b0d05c17c2082d02 (patch)
tree04b0bbedba8b34ef187a5df895cb1cff9a877728 /doc/src
parent54cd4f04576833abc394e131288bf3dd7dcf4806 (diff)
downloadpostgresql-ed437e2b27c48219a78f3504b0d05c17c2082d02.tar.gz
postgresql-ed437e2b27c48219a78f3504b0d05c17c2082d02.zip
Adjust comments about avoiding use of printf's %.*s.
My initial impression that glibc was measuring the precision in characters (which is what the Linux man page says it does) was incorrect. It does take the precision to be in bytes, but it also tries to truncate the string at a character boundary. The bottom line remains the same: it will mess up if the string is not in the encoding it expects, so we need to avoid %.*s anytime there's a significant risk of that. Previous code changes are still good, but adjust the comments to reflect this knowledge. Per research by Hernan Gonzalez.
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions