aboutsummaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_gist.sql.in
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-11-09 20:10:02 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-11-09 20:10:02 +0000
commita96fa85025f8b6da15cd2227712bd47b94f9c3f2 (patch)
tree8f4db30ae0fb14b3af85a0da993717a7407092ed /contrib/btree_gist/btree_gist.sql.in
parent4b606ee444a1663a5ae668f5cd0560f165b04c43 (diff)
downloadpostgresql-a96fa85025f8b6da15cd2227712bd47b94f9c3f2.tar.gz
postgresql-a96fa85025f8b6da15cd2227712bd47b94f9c3f2.zip
Second pass at improving LIKE/regex estimation in non-C locales. It turns
out that it's actually quite likely that a string that is an extension of the given prefix will sort as larger than the "greater" string our previous code created. To provide some defense against that, do the comparisons against a modified string instead of just the bare prefix. We tack on "Z", "z", "y", or "9", whichever is seen as largest in the current locale. Testing suggests that this is sufficient at least for cases involving ASCII data.
Diffstat (limited to 'contrib/btree_gist/btree_gist.sql.in')
0 files changed, 0 insertions, 0 deletions