# Restore failed \`entity2char already exists' RDS Postgres 13.7

**URL:** https://meta.discourse.org/t/restore-failed-entity2char-already-exists-rds-postgres-13-7/245964
**Category:** Self-hosting
**Created:** [November 17, 2022, 8:43pm UTC](https://meta.discourse.org/t/restore-failed-entity2char-already-exists-rds-postgres-13-7/245964 "2022-11-17T20:43:16Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 19, 2022, 1:50am UTC](https://meta.discourse.org/t/restore-failed-entity2char-already-exists-rds-postgres-13-7/245964/9 "2022-11-19T01:50:49Z")

</div>

The solution was to drop, create, and migrate the database before doing the restore. I should have tried skipping the migrate step.

Thanks for your help, @RGJ and @gerhard. Your clues were helpful in my figuring this out.

I guess the reason not to always drop the database first is that you can’t then back out when it fails.

---

_[View the full topic](https://meta.discourse.org/t/restore-failed-entity2char-already-exists-rds-postgres-13-7/245964)._