# Update = ☠

**URL:** https://meta.discourse.org/t/update/285222
**Category:** Self-hosting
**Created:** [November 11, 2023, 11:42pm UTC](https://meta.discourse.org/t/update/285222 "2023-11-11T23:42:48Z")
**Posts on this page:** 1
**Showing post:** 37

<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 16, 2023, 3:01pm UTC](https://meta.discourse.org/t/update/285222/37 "2023-11-16T15:01:10Z")

</div>

A few things if someone else gets stuck this way.

First, don’t run a `./launcher cleanup`, instead run a `./launcher start app` to restart your existing container. Then you’d be able to do something like

```plaintext
./launcher enter app
su - postgres
psql discourse
drop table ...

```

Without the container to enter and talk direclty to postgres, you have to do it during the container build by adding something like this to your `app.yml`:

```plaintext
hooks:
  after_postgres:
      - exec: /bin/bash -c 'sudo -u postgres psql discourse <<< "drop table summary_sections;"'
      - exec: /bin/bash -c 'sudo -u postgres psql discourse <<< "drop table theme_settings_migrations;"'

```

I don’t know how it was that those two tables got created such that the migrations were out of whack, but this was a fix. And it was stranger than that, because the database had somehow been wiped and once I fixed this it was a brand new database, so it must have somehow been stopped in the middle of a migration at some point.

---

_[View the full topic](https://meta.discourse.org/t/update/285222)._