X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id CFDBD9DD61C
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Tue,  6 Dec 2005 17:00:35 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 91810-04
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Tue,  6 Dec 2005 17:00:36 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from candle.pha.pa.us (candle.pha.pa.us [64.139.89.126])
	by postgresql.org (Postfix) with ESMTP id AEEDD9DCC0B
	for <pgsql-hackers@postgresql.org>;
	Tue,  6 Dec 2005 17:00:32 -0400 (AST)
Received: (from pgman@localhost)
	by candle.pha.pa.us (8.11.6/8.11.6) id jB6L0ZF08711;
	Tue, 6 Dec 2005 16:00:35 -0500 (EST)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200512062100.jB6L0ZF08711@candle.pha.pa.us>
Subject: Re: Upcoming PG re-releases
In-Reply-To: <200512062147.26826.peter_e@gmx.net>
To: Peter Eisentraut <peter_e@gmx.net>
Date: Tue, 6 Dec 2005 16:00:35 -0500 (EST)
CC: pgsql-hackers@postgresql.org
X-Mailer: ELM [version 2.4ME+ PL121 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.007 required=5 tests=[AWL=0.007]
X-Spam-Score: 0.007
X-Spam-Level: 
X-Archive-Number: 200512/336
X-Sequence-Number: 77184


Nice, updated.

---------------------------------------------------------------------------

Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > One nice solution would be if iconv would report the lines with
> > errors and you could correct them, but I see no way to do that.  The
> > only thing you could do is to diff the old and new files to see the
> > problems.  Is that helpful?  Here is new text I have used:
> 
> I think this is nice.  It users see a big mess, they will have to clean
> it up by hand anyway.
> 
> How about this for better wording:
> 
> diff -u -3 -p -r1.400.2.4 release.sgml
> --- doc/src/sgml/release.sgml   6 Dec 2005 20:26:02 -0000       1.400.2.4
> +++ doc/src/sgml/release.sgml   6 Dec 2005 20:44:26 -0000
> @@ -528,15 +528,16 @@ psql -t -f fixseq.sql db1 | psql -e db1
> 
>       <listitem>
>        <para>
> -       Some users are having problems loading <literal>UTF8</> data into
> -       8.1.X.  This is because previous versions allowed invalid <literal>UTF8</>
> +       Some users are having problems loading UTF-8 data into
> +       8.1.X.  This is because previous versions allowed invalid UTF-8 byte
>         sequences to be entered into the database, and this release
> -       properly accepts only valid <literal>UTF8</> sequences.  One
> -       way to correct a dumpfile is to use <command>iconv -c -f UTF-8 -t UTF-8
> +       properly accepts only valid UTF-8 sequences.  One
> +       way to correct a dumpfile is to run the command <command>iconv -c -f UTF-8 -t UTF-8
>         -o cleanfile.sql dumpfile.sql</>.  The <literal>-c</> option removes
>         invalid character sequences.  A diff of the two files will show the
>         sequences that are invalid.  <command>iconv</> reads the entire input
> -       file into memory so it might be necessary to <command>split</> the dump
> +       file into memory so it might be necessary to use <command>split</>
> +       to break up the dump
>         into multiple smaller files for processing.
>        </para>
>       </listitem>
> 
> -- 
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073