Problemas de acesso ao banco de dados após atualização v3.5.2 -> v3.6.0.beta2

[pfaffman (Jay Pfaffman)]

Did you follow these instructions? (It doesn’t seem like it?)

@Discourse

hooks:
  after_postgres:
     - exec: sudo -u postgres createdb b_discourse || exit 0
     - exec:
          stdin: |
            grant all privileges on database b_discourse to discourse;
          cmd: sudo -u postgres psql b_discourse
          raise_on_fail: false

     - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "alter schema public owner to discourse;"'
     - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "create extension if not exists hstore;"'
     - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "create extension if not exists pg_trgm;"'
.......

@Stew_Pid

Will simply changing owner to discourse fix it?

It’s a pretty good bet, but make sure that you’ve got stuff like in the multisite install topic.

If your sites are working now then I too would encourage you to do a clean multisite install and backup/restore the databases over. You can copy all the other stuff as described in Move a Discourse site to another VPS with rsync