Peter Eisentraut <peter_e@xxxxxxx> writes: > I guess you could get around that if you leave the case-folding in the > lexer as is but instead make the nameeq function case insensitive. If you do that then you have to nail down the behavior at initdb time (else flipping the switch will corrupt all your system catalog indexes). To be selective about which occurrences of identifiers get smashed to lower, I think we would have to postpone the smashing into analyze.c. This would be a lot messier than doing it once in the lexer --- but on the other hand, it would avoid violating the rule stated in gram.y, namely that lexer and grammar behavior must not vary depending on GUC variable settings. On the third hand, we could get around that restriction by not allowing the GUC variable to change within a session, which might be a good idea anyway to avoid confusing applications. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
