[Rt-commit] rt branch, 4.0/pg-9.2-compatibility, updated. rt-4.0.13-55-gcdd71cc

[Kevin Falcone]

The branch, 4.0/pg-9.2-compatibility has been updated
       via  cdd71ccbc41d7a292b81230a42e80dbc1409fb75 (commit)
      from  38c965f5726218bbd6636f6455f07241d980cff2 (commit)

Summary of changes:
 docs/UPGRADING-4.0 | 12 ++++++++++++
 1 file changed, 12 insertions(+)

- Log -----------------------------------------------------------------
commit cdd71ccbc41d7a292b81230a42e80dbc1409fb75
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Mon Jul 8 17:44:29 2013 -0400

    Document the new DBD::Pg requirement
    
    Hopefully folks will install the newer DBD::Pg before upgrading, but if
    they don't, document how to re-start since the presence of a schema file
    makes it impossible to just restart the make upgrade-database.

diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0
index 9bca8f1..89141f9 100644
--- a/docs/UPGRADING-4.0
+++ b/docs/UPGRADING-4.0
@@ -205,3 +205,15 @@ solution of resorting to defining all queues in
 $OverrideOutgoingMailFrom.  Any definitions in the Override option
 (including Default) still take precedence.  See
 L<RT_Config/$SetOutgoingMailFrom> for more information.
+
+If you are upgrading an RT from 3.8 (or earlier) to 4.0 on PostgreSQL
+9.2, you should make sure that you have installed DBD::Pg 2.19.3 or
+higher.  If you start your upgrade without installing a recent-enough
+version of DBD::Pg RT will stop the upgrade during the 3.9.8 step and
+remind you to upgrade DBD::Pg.  If this happens, you can re-start your
+upgrade by running:
+
+   ./sbin/rt-setup-database --action insert --datadir etc/upgrade/3.9.8/
+
+Followed by re-running make upgrade-database and answering 3.9.8 when
+prompted for which RT version you're upgrading from.

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