Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C3437475E1F for ; Fri, 25 Oct 2002 10:37:57 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 1F887475DFD for ; Fri, 25 Oct 2002 10:37:57 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g9PEbxhR022965; Fri, 25 Oct 2002 10:37:59 -0400 (EDT) To: Tim Perdue Cc: pgsql-sql@postgresql.org Subject: Re: Foreign character struggles In-reply-to: <20021025083259.B29164@mail.perdue.net> References: <20021025083259.B29164@mail.perdue.net> Comments: In-reply-to Tim Perdue message dated "Fri, 25 Oct 2002 08:33:00 -0500" Date: Fri, 25 Oct 2002 10:37:59 -0400 Message-ID: <22964.1035556679@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/357 X-Sequence-Number: 10074 Tim Perdue writes: > I compiled postgres with --enable-multibyte and --enable-recode, and it > doesn't appear to help with my problem. I think this is a locale issue, not a character set issue. You definitely need --enable-locale, but I doubt you need either of the above (unless you need to deal with Unicode or Far-Eastern languages). > If an end-user types plain-english Sao Paulo, I want the database to pull up > "São Paulo", essentially just treating the accented characters as if they were > regular ASCII. I'd suggest matching on "upper(city)" to get rid of accents; given the right locale setting that should work, and you can add a functional index to make it fast. > Also, my "Up Arrow" and "Delete" keys no longer work since I recompiled 7.2.3 > on debian. You are missing libreadline. regards, tom lane