X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7B1803A3B4B for ; Tue, 16 Nov 2004 08:37:24 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 25170-10 for ; Tue, 16 Nov 2004 08:37:14 +0000 (GMT) Received: from web11.manitu.net (web11.manitu.net [217.11.48.111]) by svr1.postgresql.org (Postfix) with ESMTP id 25EE73A3B4C for ; Tue, 16 Nov 2004 08:37:13 +0000 (GMT) Received: from localhost (dsl-082-082-067-080.arcor-ip.net [82.82.67.80]) by web11.manitu.net (8.10.2-SOL3/8.10.2) with ESMTP id iAG8awX14648; Tue, 16 Nov 2004 09:36:58 +0100 Subject: Re: evil characters #bfef cause dump failure From: Markus Bertheau To: Tom Lane Cc: Iain , Christian Fowler , pgsql-admin list In-Reply-To: <12470.1100568891@sss.pgh.pa.us> References: <9996.1100547889@sss.pgh.pa.us> <10478.1100550946@sss.pgh.pa.us> <10656.1100552422@sss.pgh.pa.us> <007901c4cb7a$1cbddcb0$7201a8c0@mst1x5r347kymb> <12470.1100568891@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8 Date: Tue, 16 Nov 2004 09:37:01 +0100 Message-Id: <1100594222.3393.0.camel@fc3> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/127 X-Sequence-Number: 15511 В Пнд, 15/11/2004 в 20:34 -0500, Tom Lane пишет: > "Iain" writes: > > It seems that this kind of thing pops up from time to time. I don't have v8 > > available right now to check, but is SQL_ASCII still the default DB > > encoding? I'm wondering is unicode wouldn't be a better choice these days. > > IIRC you can select the default encoding at build time, so this is > really a question for packagers not the development team. > > You make a good point though --- I'm a bit tempted to make it default to > UNICODE for the Red Hat build, since Red Hat is pretty gung-ho on UTF8 > support these days. > > BTW, SQL_ASCII is not so much an encoding as the absence of any encoding > choice; it just passes 8-bit data with no interpretation. So it's not > *that* unreasonable a default. You can store UTF8 data in it without > any problem, you just won't have the niceties like detection of bad > character sequences. This is, by the way, a reason why this encoding should be renamed to SQL_8BIT (or something along these lines) and UNICODE to UTF-8. -- Markus Bertheau