diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-05-08 16:40:45 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-05-08 16:40:45 +0000 |
commit | 350c7f208f4123f713ec5ba45e14f8439e98615b (patch) | |
tree | 9baa981b1e7f25dcd6e0b151540c7d394a03a684 /src/backend/parser/parse_clause.c | |
parent | f9a60d1542d21f2caf9a51b249dde63054bd9272 (diff) | |
download | postgresql-350c7f208f4123f713ec5ba45e14f8439e98615b.tar.gz postgresql-350c7f208f4123f713ec5ba45e14f8439e98615b.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/parser/parse_clause.c')
0 files changed, 0 insertions, 0 deletions