increase required Postgres version to 9.2

docs/DEVELOPER-ADVANCED.md

@@ -82,11 +82,11 @@ Vagrant version 1.1.2. With this Vagrantfile:
     echo "gem: --no-document" >> /etc/gemrc
     su - vagrant -c "echo 'gem: --no-document' >> ~/.gemrc"
 
-## Postgres 9.1
+## Postgres 9.2
 
 Configure so that the vagrant user doesn't need to provide username and password.
 
-    apt-get -yqq install postgresql postgresql-contrib-9.1 libpq-dev postgresql-server-dev-9.1
+    apt-get -yqq install postgresql postgresql-contrib-9.3 libpq-dev postgresql-server-dev-9.3
     su - postgres
     createuser --createdb --superuser -Upostgres vagrant
     psql -c "ALTER USER vagrant WITH PASSWORD 'password';"

docs/INSTALL.md

@@ -20,7 +20,7 @@ Hosting Rails applications is complicated. Even if you already have Postgres, Re
 
 ### Software Requirements
 
-- [Postgres 9.1+](http://www.postgresql.org/download/)
+- [Postgres 9.2+](http://www.postgresql.org/download/)
 - [Redis 2.6+](http://redis.io/download)
 - [Ruby 2.0+](http://www.ruby-lang.org/en/downloads/) (we recommend 2.0.0-p353 or higher)
 

docs/TROUBLESHOOTING-prod.md

@@ -12,7 +12,7 @@ something like:
     `ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-linux]`
 
 
-1. Are you on Postgres 9.1 or later with HSTORE enabled?
+1. Are you on Postgres 9.2 or later with HSTORE enabled?
 
    You can check your postgres version by typing `psql --version`. To see if
 hstore is installed, open a session to postgres and type `\dx` and see if
@@ -50,7 +50,7 @@ should *always* pass every test.
    If links in emails have localhost in them, then you are still using the
 default `host_names` value in database.yml.  Update it to use your site's host
 name(s).
-   
+
 1. Are you having problems bundling:
 
 ```

docs/TROUBLESHOOTING.md

@@ -6,11 +6,11 @@ reaching out to the community for help:
 
 1. Are you running Ruby 2.0 or later?
 
-   Discourse is designed for Ruby 2.0 or later. We recommend 2.0.0 p353 or later. You can check your version by typing 
+   Discourse is designed for Ruby 2.0 or later. We recommend 2.0.0 p353 or later. You can check your version by typing
    `ruby -v` and checking the response.
 
 
-2. Are you on Postgres 9.1 or later with HSTORE enabled?
+2. Are you on Postgres 9.2 or later with HSTORE enabled?
 
    You can check your postgres version by typing `psql --version`. To see if hstore is
    installed, open a session to postgres and type `\dx` and see if hstore is listed.
@@ -30,21 +30,21 @@ reaching out to the community for help:
 
 5. Have you migrated your database?
 
-   Our schema changes fairly frequently. After checking out the source code, you should 
+   Our schema changes fairly frequently. After checking out the source code, you should
    run `rake db:migrate`
 
 7. Do the tests pass?
 
-   If you are having other problems, it's useful to know if the test suite passes. You 
-   can run it by first using `rake db:test:prepare` and then `rake spec`. If you 
-   experience any failures, that's a bad sign! Our master branch should *always* pass 
+   If you are having other problems, it's useful to know if the test suite passes. You
+   can run it by first using `rake db:test:prepare` and then `rake spec`. If you
+   experience any failures, that's a bad sign! Our master branch should *always* pass
    every test.
 
 8. Have you updated host_names in your database.yml?
 
    If links in emails have localhost in them, then you are still using the default host_names
    value in database.yml.  Update it to use your site's host name(s).
-   
+
 9. Are you having problems bundling:
 
 ```