# Discourse Upgrade from 3.2.0 to 3.3.0 Postgress issue

**URL:** <https://meta.discourse.org/t/discourse-upgrade-from-3-2-0-to-3-3-0-postgress-issue/323034>\
**Category:** Self-hosting\
**Created:** [August 23, 2024, 8:40am UTC](https://meta.discourse.org/t/discourse-upgrade-from-3-2-0-to-3-3-0-postgress-issue/323034 "2024-08-23T08:40:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\
**Post date:** [October 24, 2024, 10:42am UTC](https://meta.discourse.org/t/discourse-upgrade-from-3-2-0-to-3-3-0-postgress-issue/323034/3 "2024-10-24T10:42:01Z")

</div>

I’m closing that PR because I can’t reproduce the issue and nobody else reported a similar issue.

`Migration::ColumnDropper.execute_drop` drops the `read_only` function for each column with `CASCADE`. That also drops the trigger.

It sounds like you had a trigger that didn’t reference the `read_only` function. I’m not sure how you managed to do this. Are you using a [standard install](https://meta.discourse.org/t/142537?silent=true)?

---

_[View the full topic](https://meta.discourse.org/t/discourse-upgrade-from-3-2-0-to-3-3-0-postgress-issue/323034)._