Re: pg_dump error - LOCALIZATION PROBLEM

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Erol Öz <eroloz(at)esg(dot)com(dot)tr>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump error - LOCALIZATION PROBLEM
Date: 2001-09-16 23:04:18
Message-ID: Pine.LNX.4.30.0109170100180.856-100000@peter.localdomain
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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 strcasecmp() call suspicious. In many places an
ASCII-only alternative is needed or the code needs to be rewritten.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-09-16 23:18:18 Re: pg_dump error - LOCALIZATION PROBLEM
Previous Message Bolt Thrower 2001-09-16 22:23:15 sequences: log_cnt?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-09-16 23:18:18 Re: pg_dump error - LOCALIZATION PROBLEM
Previous Message Tom Lane 2001-09-16 21:57:39 Re: pg_dump error - LOCALIZATION PROBLEM