summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-10-06 11:18:32 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2022-10-06 11:18:32 -0400
commit58640f37d9acf632a4dd60d140f36f2e6815f716 (patch)
treec37eeaa21a221e717bef931dec2724a560b7247f /src/backend/access/gist/gistproc.c
parentca71131eebba63809ceb86be033a264a5f0a1d79 (diff)
downloadpostgresql-58640f37d9acf632a4dd60d140f36f2e6815f716.tar.gz
Remove useless character-length checks in contrib/ltree.
The t_iseq() macro does not need to be guarded by a character length check (at least when the comparison value is an ASCII character, as its documentation requires). Some portions of contrib/ltree hadn't read that memo, so simplify them. The last change in gettoken_query, - else if (charlen == 1 && !t_iseq(state->buf, ' ')) + else if (!t_iseq(state->buf, ' ')) looks like it's actually a bug fix: I doubt that the intention was to silently ignore multibyte characters as if they were whitespace. I'm not tempted to back-patch though, because this will have the effect of tightening what is allowed in ltxtquery strings. Discussion: https://postgr.es/m/2548310.1664999615@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions