Re: Upcoming PG re-releases

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Upcoming PG re-releases
Date: 2005-12-06 21:00:35
Message-ID: 200512062100.jB6L0ZF08711@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www


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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-12-06 21:01:57 Re: Concurrent CREATE INDEX, try 2 (was Re: Reducing
Previous Message Hannu Krosing 2005-12-06 20:58:06 Re: Concurrent CREATE INDEX, try 2 (was Re: Reducing

Browse pgsql-www by date

  From Date Subject
Next Message Dave Page 2005-12-06 22:36:19 Re: Launching PostgreSQL KB Project Mark 2
Previous Message Gevik babakhani 2005-12-06 20:54:08 Re: Launching PostgreSQL KB Project Mark 2