Tue Dec 13 19:40:46 PST 2005
- Previous message: [Slony1-commit] By cbbrowne: Expressly add plpgsql to new DBs
- Next message: [Slony1-commit] By cbbrowne: Update docs for NG testbed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message:
-----------
Documentation for 1.1.5:
- Tries to use TRUNCATE
- Add discussion of encodings, a place where PG 8.1 can break
Tags:
----
REL_1_1_STABLE
Modified Files:
--------------
slony1-engine:
RELEASE-1.1.5 (r1.1.2.2 -> r1.1.2.3)
-------------- next part --------------
Index: RELEASE-1.1.5
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/Attic/RELEASE-1.1.5,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -LRELEASE-1.1.5 -LRELEASE-1.1.5 -u -w -r1.1.2.2 -r1.1.2.3
--- RELEASE-1.1.5
+++ RELEASE-1.1.5
@@ -28,6 +28,9 @@
6. A fairly large number of minor bugs that have been reported have
been fixed.
+7. If possible, use TRUNCATE during SUBSCRIBE SET to empty out tables
+on subscribers.
+
*** OUTSTANDING ISSUE WITH PostgreSQL 8.1 ***
@@ -64,3 +67,28 @@
In view of the risks, running replication between versions seems to be
something you should not keep running any longer than is necessary to
migrate to 8.1.
+
+http://archives.postgresql.org/pgsql-hackers/2005-12/msg00181.php
+
+Extracting from that:
+---------------------------------------------------------------
+Upgrading UNICODE databases to 8.1
+
+Postgres 8.1 includes a number of bug-fixes and improvements to
+Unicode and UTF-8 character handling. Unfortunately previous releases
+would accept character sequences that were not valid UTF-8. This
+may cause problems when upgrading your database using
+pg_dump/pg_restore resulting in an error message like this:
+
+ Invalid UNICODE byte sequence detected near byte ...
+
+To convert your pre-8.1 database to 8.1 you may have to remove and/or
+fix the offending characters. One simple way to fix the problem is to
+run your pg_dump output through the iconv command like this:
+
+ iconv -c -f UTF8 -t UTF8 -o fixed.sql dump.sql
+
+The -c flag tells iconv to omit invalid characters from output.
+
+-- Paul Lindner
+---------------------------------------------------------------
\ No newline at end of file
- Previous message: [Slony1-commit] By cbbrowne: Expressly add plpgsql to new DBs
- Next message: [Slony1-commit] By cbbrowne: Update docs for NG testbed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list