aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeMergejoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-05-08 16:40:03 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-05-08 16:40:03 +0000
commit191c52a27b30b12e354c86dac0f31000dcccd3ad (patch)
tree219ba7f43384675bc1e1f50f55091ff7df4f777e /src/backend/executor/nodeMergejoin.c
parentaa4a0e6fc38e5842b972256c97d5ad34e246db27 (diff)
downloadpostgresql-191c52a27b30b12e354c86dac0f31000dcccd3ad.tar.gz
postgresql-191c52a27b30b12e354c86dac0f31000dcccd3ad.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/executor/nodeMergejoin.c')
0 files changed, 0 insertions, 0 deletions