>> Hmm. Given that we expect the lexer to have downcased any unquoted
>> words, this seems like a workable solution --- where else are we using
>> strcasecmp() unnecessarily?
Wait a minute --- I spoke too quickly. The lexer's behavior is to
downcase unquoted identifiers in a *locale sensitive*
Tom Lane writes:
> Hmm. Given that we expect the lexer to have downcased any unquoted
> words, this seems like a workable solution --- where else are we using
> strcasecmp() unnecessarily?
I've identified several other such places. However, in reality we have to
consider every single strcasecm
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Untested, but try this:
> Edit src/backend/commands/variable.c, look for the function
> parse_XactIsoLevel(). Change the code that looks like this:
> if (strcasecmp(value, "SERIALIZABLE") == 0)
> XactIsoLevel = XACT_SERIALIZ
Erol Öz writes:
> I think Tom Lane is right as always. My postgresql server was
> configured with --enable-locale option and it works perfect with
> Turkish stuff. However I could not find a solution to the problem
> below.
Untested, but try this:
Edit src/backend/commands/variable.c, look for
Hi,
It worked.
Thanks a lot.
Regards
Erol
-Özgün Ýleti-
Kimden: Peter Eisentraut <[EMAIL PROTECTED]>
Kime: Erol Öz <[EMAIL PROTECTED]>
Bilgi: PostgreSQL General List <[EMAIL PROTECTED]>
Tarih: 14 Eylül 2001 Cuma 18:03
Konu: Re: [GENERAL] pg_dump error - LOCALIZATION
