[Rt-commit] rt branch, 4.2-trunk, updated. rt-4.2.9-2-gc6abab7

[Kevin Falcone]

The branch, 4.2-trunk has been updated
       via  c6abab710abc74a02319185234900d13635944fd (commit)
      from  4decb462de3b99a7be715cc19098c369348f198c (commit)

Summary of changes:
 docs/backups.pod | 7 +++++++
 1 file changed, 7 insertions(+)

- Log -----------------------------------------------------------------
commit c6abab710abc74a02319185234900d13635944fd
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Thu Oct 30 12:51:10 2014 -0400

    Tell admins to analyze their indexes after a restore
    
    Otherwise the Postgres planner may make some crazy estimates and perform
    poorly.

diff --git a/docs/backups.pod b/docs/backups.pod
index 16ba5b0..554336f 100644
--- a/docs/backups.pod
+++ b/docs/backups.pod
@@ -137,6 +137,13 @@ and insert data and configure rights for the rt_user.
 
     gunzip -c rt-20141014.sql.gz | psql rt4
 
+=item After Restoring
+
+Postgres will generally perform poorly after restoring from backups
+because it has outdated index statistics. You should run C<analyze>
+after your restore is complete. If you'd like to watch the progress, you
+can run C<analyze verbose>.
+
 =back
 
 =head2 FILESYSTEM

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