pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Iain <iain@mst.co.jp>
Cc: Christian Fowler <spider@viovio.com>
Cc: pgsql-admin list <pgsql-admin@postgresql.org>
Subject: Re: evil characters #bfef cause dump failure
Date: Mon, 15 Nov 2004 20:34:51 -0500
Message-ID: <12470.1100568891@sss.pgh.pa.us> (raw)
In-Reply-To: <007901c4cb7a$1cbddcb0$7201a8c0@mst1x5r347kymb>
References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com>
	<9996.1100547889@sss.pgh.pa.us>
	<Pine.LNX.4.61.0411151527550.12980@leda.steelsun.com>
	<10478.1100550946@sss.pgh.pa.us>
	<Pine.LNX.4.61.0411151539540.12980@leda.steelsun.com>
	<10656.1100552422@sss.pgh.pa.us>
	<007901c4cb7a$1cbddcb0$7201a8c0@mst1x5r347kymb>

"Iain" <iain@mst.co.jp> 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.

			regards, tom lane



view thread (16+ messages)  latest in thread

Message-ID: <12470.1100568891@sss.pgh.pa.us>
Permalink:  ../12470.1100568891@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12470.1100568891@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, iain@mst.co.jp, spider@viovio.com
  Subject: Re: evil characters #bfef cause dump failure
  In-Reply-To: <12470.1100568891@sss.pgh.pa.us>
  References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com> <9996.1100547889@sss.pgh.pa.us> <Pine.LNX.4.61.0411151527550.12980@leda.steelsun.com> <10478.1100550946@sss.pgh.pa.us> <Pine.LNX.4.61.0411151539540.12980@leda.steelsun.com> <10656.1100552422@sss.pgh.pa.us> <007901c4cb7a$1cbddcb0$7201a8c0@mst1x5r347kymb> <12470.1100568891@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox