# Problema ao restaurar Discourse a partir de backup (3.4, banco de dados bastante grande)

**URL:** <https://meta.discourse.org/t/problem-with-restore-discourse-from-backup-3-4-quite-large-db/346497>\
**Category:** Product Support\
**Created:** [Janeiro 10, 2025, 11:08am UTC](https://meta.discourse.org/t/problem-with-restore-discourse-from-backup-3-4-quite-large-db/346497 "2025-01-10T11:08:42Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)\
**Post date:** [Janeiro 14, 2025, 11:33am UTC](https://meta.discourse.org/t/problem-with-restore-discourse-from-backup-3-4-quite-large-db/346497/18 "2025-01-14T11:33:08Z")

</div>

Acho que você precisa atualizar o script manual desta forma:

DROP SCHEMA public CASCADE;  
CREATE SCHEMA public;  
ALTER SCHEMA public OWNER TO discourse;  
CREATE EXTENSION IF NOT EXISTS hstore;  
CREATE EXTENSION IF NOT EXISTS pg\_trgm;  
END;

Não há necessidade de CREATE SCHEMA public (e definir o proprietário), pois o Pg mais recente cria o esquema a partir do dump de backup do SQL.  
No entanto, as permissões da tabela devem ser corrigidas para o usuário discourse, por padrão elas são postgres.

Agora funciona! Obrigado a todos pelas ideias e apoio.

---

_[View the full topic](https://meta.discourse.org/t/problem-with-restore-discourse-from-backup-3-4-quite-large-db/346497)._