# Update problem : Broken Forum

**URL:** <https://meta.discourse.org/t/update-problem-broken-forum/222055>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [March 26, 2022, 8:20pm UTC](https://meta.discourse.org/t/update-problem-broken-forum/222055 "2022-03-26T20:20:17Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![mint\_saxon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mint_saxon/32/167253_2.png) [@mint\_saxon](https://meta.discourse.org/u/mint_saxon)\
**Post date:** [April 2, 2022, 1:24pm UTC](https://meta.discourse.org/t/update-problem-broken-forum/222055/21 "2022-04-02T13:24:05Z")

</div>

We’re also seeing this behaviour, also a standard Discourse install that’s been running for several years without problems.

My theory is that there’s a problem with the database migration which tries to add a Postgres extension; from the traceback during `./launcher rebuild` I see

`/var/www/discourse/db/migrate/20220304162250_enable_unaccent_extension.rb:5:in `change’`

I wonder if this migration should follow the same format as e.g. `db/migrate/20120924182000_add_hstore_extension.rb`?

`I, [2022-04-02T12:49:18.895537 #1] INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists pg_trgm;"' NOTICE: extension "pg_trgm" already exists, skipping I, [2022-04-02T12:49:18.984635 #1] INFO -- : CREATE EXTENSION`

@RGJ do you have any advice on trying out this change?

---

_[View the full topic](https://meta.discourse.org/t/update-problem-broken-forum/222055)._