pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christian Fowler <spider@viovio.com>
To: pgsql-admin list <pgsql-admin@postgresql.org>
Subject: Re: evil characters #bfef cause dump failure
Date: Tue, 16 Nov 2004 11:06:50 -0500 (EST)
Message-ID: <Pine.LNX.4.61.0411161057120.16733@leda.steelsun.com> (raw)
In-Reply-To: <1100594222.3393.0.camel@fc3>
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>
	<1100594222.3393.0.camel@fc3>


I strongly agree with this. I have always been uncomfortable selecting 
"UNICODE" and never quite sure if it is the UTF8, UTF16, or UTF32 
encoding.

SQL_8BIT or SQL_RAW make much more sense than SQL_ASCII given that Tom 
said this is a lack of encoding. I fear I might have high-bits chopped off 
or something.

However, back to my problem... if a #bfef character is shoved into a 
VARCHAR, one's dump is hosed. If I went to various websites and entered 
this in, I could cause a lot of pain. I believe I noticed some characters 
(like new line and tab) are converted to <80> or similar. Could/should 
this be extended to more character ranges - particularly high byte chars 
for people with the SQL_ASCII (lackof) encoding?


On Tue, 16 Nov 2004, Markus Bertheau wrote:

>
> 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 <twanger@bluetwanger.de>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>

[ \ /
[ >X<   Christian Fowler      | spider AT viovio.com
[ / \   http://www.viovio.com | http://www.tikipro.org



view thread (16+ messages)

Message-ID: <Pine.LNX.4.61.0411161057120.16733@leda.steelsun.com>
Permalink:  ../Pine.LNX.4.61.0411161057120.16733@leda.steelsun.com/
Also on:    postgresql.org/message-id/Pine.LNX.4.61.0411161057120.16733@leda.steelsun.com

 · 

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: spider@viovio.com
  Subject: Re: evil characters #bfef cause dump failure
  In-Reply-To: <Pine.LNX.4.61.0411161057120.16733@leda.steelsun.com>
  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> <1100594222.3393.0.camel@fc3> <Pine.LNX.4.61.0411161057120.16733@leda.steelsun.com>

* 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