aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-08-21 16:55:51 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-08-21 16:55:51 +0000
commit95cacd1345c4d1b00fe6cc7fff58c7391ce907d6 (patch)
treebb0ba28a38ff957e7d70fdc74a7630d0da3ffb21 /src/backend/access/gist/gistproc.c
parentc5d6d5bc6d23b6ebd6cb17d401e10581cd112c20 (diff)
downloadpostgresql-95cacd1345c4d1b00fe6cc7fff58c7391ce907d6.tar.gz
postgresql-95cacd1345c4d1b00fe6cc7fff58c7391ce907d6.zip
Use a non-locale-dependent definition of isspace() in array_in/array_out.
array_in discards unquoted leading and trailing whitespace in array values, while array_out is careful to quote array elements that contain whitespace. This is problematic when the definition of "whitespace" varies between locales: array_in could drop characters that were meant to be part of the value. To avoid that, lock down "whitespace" to mean only the traditional six ASCII space characters. This change also works around a bug in OS X and some older BSD systems, in which isspace() could return true for character fragments in UTF8 locales. (There may be other places in PG where that bug could cause problems, but this is the only one complained of so far; see recent report from Steven Schlansker.) Back-patch to 9.0, but not further. Given the lack of previous reports of trouble, changing this behavior in stable branches seems to offer more risk of breaking applications than reward of avoiding problems.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions