aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistsplit.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-05-08 16:40:31 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-05-08 16:40:31 +0000
commit27594103806c8e209993f31a50d91d7add968b2f (patch)
treefc415f9f8e6d086e39b21c81d644f7a6566ab994 /src/backend/access/gist/gistsplit.c
parente7a03793d86e155664bad149f570da5d7743983a (diff)
downloadpostgresql-27594103806c8e209993f31a50d91d7add968b2f.tar.gz
postgresql-27594103806c8e209993f31a50d91d7add968b2f.zip
Work around a subtle portability problem in use of printf %s format.
Depending on which spec you read, field widths and precisions in %s may be counted either in bytes or characters. Our code was assuming bytes, which is wrong at least for glibc's implementation, and in any case libc might have a different idea of the prevailing encoding than we do. Hence, for portable results we must avoid using anything more complex than just "%s" unless the string to be printed is known to be all-ASCII. This patch fixes the cases I could find, including the psql formatting failure reported by Hernan Gonzalez. In HEAD only, I also added comments to some places where it appears safe to continue using "%.*s".
Diffstat (limited to 'src/backend/access/gist/gistsplit.c')
0 files changed, 0 insertions, 0 deletions