From owner-freebsd-stable@FreeBSD.ORG  Mon Mar 20 16:59:25 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: stable@freebsd.org
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4BC3416A401
	for <stable@freebsd.org>; Mon, 20 Mar 2006 16:59:25 +0000 (UTC)
	(envelope-from vivek@khera.org)
Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0E4B143D45
	for <stable@freebsd.org>; Mon, 20 Mar 2006 16:59:25 +0000 (GMT)
	(envelope-from vivek@khera.org)
Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103])
	by yertle.kcilink.com (Postfix) with ESMTP id 58C17B80C
	for <stable@freebsd.org>; Mon, 20 Mar 2006 11:59:24 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v746.3)
Content-Transfer-Encoding: 7bit
Message-Id: <1CC90809-B601-425F-AA6C-9927F7EA97AA@khera.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: stable@freebsd.org
From: Vivek Khera <vivek@khera.org>
Date: Mon, 20 Mar 2006 11:59:23 -0500
X-Mailer: Apple Mail (2.746.3)
Cc: 
Subject: utf-8 support in libc?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Mar 2006 16:59:25 -0000

Reading thru one of the postgres mailing lists regarding which  
character encoding to use for a database, someone chimed in and  
claimed this:

  Umm, you should choose an encoding supported by your platform and the
  locales you use. For example, UTF-8 is a bad choice on *BSD because
  there is no collation support for UTF-8 on those platforms. On
  Linux/Glibc UTF-8 is well supported but you need to make sure the
  locale you initdb with is a UTF-8 locale. By and large postgres
  correctly autodetects the encoding from the locale.

Is this an accurate claim for FreeBSD?  I need to have a UTF-8  
encoded database in an upcoming project, and performance is always a  
concern.

Thanks.