aboutsummaryrefslogtreecommitdiff
path: root/contrib/jsonb_plpython
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-04-05 12:59:46 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-04-05 12:59:57 -0400
commit478cacb50e4851760db9b8e75b2256085b571965 (patch)
tree36953a29e1e1c05d0d789e6929934dc7b27cef96 /contrib/jsonb_plpython
parent86cc06d1cf9c30be3b79207242e6746f0f0b681c (diff)
downloadpostgresql-478cacb50e4851760db9b8e75b2256085b571965.tar.gz
postgresql-478cacb50e4851760db9b8e75b2256085b571965.zip
Ensure consistent name matching behavior in processSQLNamePattern().
Prior to v12, if you used a collation-sensitive regex feature in a pattern handled by processSQLNamePattern() (for instance, \d '\\w+' in psql), the behavior you got matched the database's default collation. Since commit 586b98fdf you'd usually get C-collation behavior, because the catalog "name"-type columns are now marked as COLLATE "C". Add explicit COLLATE specifications to restore the prior behavior. (Note for whoever writes the v12 release notes: the need for this shows that while 586b98fdf preserved pre-v12 behavior of "name" columns for simple comparison operators, it changed the behavior of regex operators on those columns. Although this patch fixes it for pattern matches generated by our own tools, user-written queries will still be affected. So we'd better mention this issue as a compatibility item.) Daniel Vérité Discussion: https://postgr.es/m/701e51f0-0ec0-4e70-a365-1958d66dd8d2@manitou-mail.org
Diffstat (limited to 'contrib/jsonb_plpython')
0 files changed, 0 insertions, 0 deletions