[prev in list] [next in list] [prev in thread] [next in thread] 

List:       slony1-commit
Subject:    [Slony1-commit] By cbbrowne: Updates to release notes...
From:       cvsuser () gborg ! postgresql ! org (CVS User Account)
Date:       2006-08-10 18:01:33
Message-ID: 20060810180133.E605311BF060 () gborg ! postgresql ! org
[Download RAW message or body]

Log Message:
-----------
Updates to release notes...

Modified Files:
--------------
    slony1-engine:
        RELEASE-1.2.0 (r1.9 -> r1.10)

-------------- next part --------------
Index: RELEASE-1.2.0
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/RELEASE-1.2.0,v
retrieving revision 1.9
retrieving revision 1.10
diff -LRELEASE-1.2.0 -LRELEASE-1.2.0 -u -w -r1.9 -r1.10
--- RELEASE-1.2.0
+++ RELEASE-1.2.0
@@ -112,6 +112,12 @@
 - A lot of fixes to the build environment (this needs to be tested on
   lots of platforms)
 
+  One noticeable upshot of this should be that (on Unix-like systems;
+  Windows(tm) appears to differ) you oughtn't need to specify a whole
+  lot of --with-pg[options] on the ./configure command line. You should
+  be able to get most of what's needed simply by specifying the path to
+  pg_config via --with-pgconfigdir.
+
 - slon "lag interval" option
 
   You can tell a node to lag behind by a particular interval of time.
@@ -146,9 +152,9 @@
   clear sl_log_1 etc.
 
 - Bug 1566 - Force all replication to occur in the ISO datestyle.
-  This ensures that we can apply date/timestamps regardless of the datestyle
-  they were entered in.
+  This ensures that we can apply date/timestamps regardless of the
+  datestyle they were entered in.
 
-- Force all replication to occur with standards_conforming_strings set to off.
-  This ensures we can replicate a node running on 8.2 without extra escape chars 
-  showing up in the data.
+- Force all replication to occur with standards_conforming_strings set
+  to off. This ensures we can replicate a node running on 8.2 without
+  extra escape chars showing up in the data.

[prev in list] [next in list] [prev in thread] [next in thread]