# Trouble upgrading from 1.9.0.beta11

**URL:** <https://meta.discourse.org/t/trouble-upgrading-from-1-9-0-beta11/105219>\
**Category:** Self-hosting\
**Created:** [28.Декабрь.2018 20:53:53 UTC](https://meta.discourse.org/t/trouble-upgrading-from-1-9-0-beta11/105219 "2018-12-28T20:53:53Z")\
**Posts on this page:** 1\
**Showing post:** 1

<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:** [28.Декабрь.2018 20:53:53 UTC](https://meta.discourse.org/t/trouble-upgrading-from-1-9-0-beta11/105219/1 "2018-12-28T20:53:53Z")

</div>

I’m trying to upgrade from `Discourse 1.9.0.beta11` that needed a postgres upgrade. Postgres upgrade seemed OK, but now rebuild fails with:

```plaintext
Caused by:                                                                                                                              
PG::DependentObjectsStillExist: ERROR: cannot drop table users column email because other objects depend on it                         
DETAIL: trigger users_email_readonly on table users depends on table users column email                                                
HINT: Use DROP ... CASCADE to drop the dependent objects too.               

```

Predictably, I can’t restore that backup to an up-to-date Discourse.

I’m not quite sure how I’d make use of the hint to `DROP ... CASCADE`.

If someone else has the problem and manages to find this, moving the `postgres_data_old` back to `postgres_data` and restarting the old container got the site back up, but I’m not sure how to get things upgraded.

This is why not to wait 14 months between upgrades, people! 😉

---

_[View the full topic](https://meta.discourse.org/t/trouble-upgrading-from-1-9-0-beta11/105219)._
