Re: [GENERAL] pg_dump error - LOCALIZATION PROBLEM
От | Tom Lane |
---|---|
Тема | Re: [GENERAL] pg_dump error - LOCALIZATION PROBLEM |
Дата | |
Msg-id | 5685.1000755583@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [GENERAL] pg_dump error - LOCALIZATION PROBLEM (Peter Eisentraut <peter_e@gmx.net>) |
Список | pgsql-hackers |
Peter Eisentraut <peter_e@gmx.net> writes: > 2. Using strcasecmp() on strings that were parsed as keywords. See CREATE > OPERATOR, CREATE AGGREGATE, CREATE TYPE, commands/define.c. But the real point is that they were parsed as identifiers, *not* keywords, and therefore have already been through a locale-dependent case conversion. (Look at what happens in scan.l after ScanKeywordLookup fails.) Unless we can undo or short-circuit that, it won't help to apply a correct ASCII-only comparison. Possibly we should change the parser's Ident node type to carry both the raw string and the downcased-as-identifier string. The latter would serve the existing needs, the former could be used for keyword matching. > For #2, we should export parts of ScanKeywordLookup as a generic function, > perhaps "normalize_identifier", ... > For #4, we need some ASCII-only strcasecmp version. I think these are the same thing. regards, tom lane
В списке pgsql-hackers по дате отправления: