Tom Lane 478cacb50e 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		2019-04-05 12:59:57 -04:00
..
.gitignore	Move psql's psqlscan.l into src/fe_utils.	2016-03-24 20:28:47 -04:00
conditional.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
logging.c	Unified logging system for command-line programs	2019-04-01 20:01:35 +02:00
Makefile	Unified logging system for command-line programs	2019-04-01 20:01:35 +02:00
mbprint.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
print.c	More unconstify use	2019-02-13 11:50:16 +01:00
psqlscan.l	Unified logging system for command-line programs	2019-04-01 20:01:35 +02:00
simple_list.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
string_utils.c	Ensure consistent name matching behavior in processSQLNamePattern().	2019-04-05 12:59:57 -04:00