Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E67382E413B for ; Thu, 7 Feb 2008 05:51:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 40533-03-5 for ; Thu, 7 Feb 2008 05:51:47 -0400 (AST) Received: from easy2.in-chemnitz.de (easy2.in-chemnitz.de [88.198.17.232]) by postgresql.org (Postfix) with ESMTP id 7C61C2E34C8 for ; Thu, 7 Feb 2008 05:17:48 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by easy2.in-chemnitz.de (Postfix) with ESMTP id 9850BB2918 for ; Thu, 7 Feb 2008 10:17:46 +0100 (CET) Received: from easy2.in-chemnitz.de ([127.0.0.1]) by localhost (easy.in-chemnitz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qnSD4ZF--Gj8 for ; Thu, 7 Feb 2008 10:17:46 +0100 (CET) Received: by easy2.in-chemnitz.de (Postfix, from userid 1013) id 86041B289B; Thu, 7 Feb 2008 10:17:46 +0100 (CET) Date: Thu, 7 Feb 2008 10:17:46 +0100 From: Tino Schwarze To: pgsql-admin@postgresql.org Subject: Re: 8.3.0, locales, and encodings Message-ID: <20080207091746.GC21225@easy2.in-chemnitz.de> References: <47AA6CEE.4010406@ultimeth.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <47AA6CEE.4010406@ultimeth.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/74 X-Sequence-Number: 28148 Hi Dean, On Wed, Feb 06, 2008 at 06:29:02PM -0800, Dean Gibson (DB Administrator) wrote: > 1. The provided /etc/init.d/postgresql file seems to be part of this > trap. Should it be changed to default the encoding to POSIX? > 2. I want my installation to have the maximum flexibility. Should I be > running INITDB w/ "-locale POSIX -E UTF8", or just "-locale POSIX" > (implying "-E SQL_ASCII")? Or does it make a difference, since I always > specify the desired database encoding when I "CREATE DATABASE... > ENCODING '...';"? AFAIK, it shouldn't make a difference. -E is just the default encoding for new databases. > 3. One of my databases is ISO-8859-1, because that's the format of the > data I get from the US gov't. However, should I instead use the 'UTF8' > encoding for that database, and then use a client (PSQL) encoding of > "LATIN1", and let PostgreSQL convert the data? Pros & cons? I'd store anything UTF8. The performance penalty should be very tiny. > I presume this ("admin") is the proper PostgreSQL list to post this to. Yes, it is. HTH, Tino. -- www.craniosacralzentrum.de www.spiritualdesign-chemnitz.de Tino Schwarze * Lortzingstraße 21 * 09119 Chemnitz