# Search 502 errors in 2.5.0.beta6

**URL:** https://meta.discourse.org/t/search-502-errors-in-2-5-0-beta6/154050
**Category:** Self-hosting
**Created:** [June 6, 2020, 10:49pm UTC](https://meta.discourse.org/t/search-502-errors-in-2-5-0-beta6/154050 "2020-06-06T22:49:24Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![ravenzachary](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ravenzachary/32/163227_2.png) [@ravenzachary](https://meta.discourse.org/u/ravenzachary)
#### Post date: [June 7, 2020, 12:33am UTC](https://meta.discourse.org/t/search-502-errors-in-2-5-0-beta6/154050/5 "2020-06-07T00:33:22Z")

</div>

Ok, I went and read this:

> [@PostgreSQL 12 update](https://meta.discourse.org/t/postgresql-12-update/151236):
>
> warning WARNING! If your database is very large, you will need a lot of extra disk space (2x database size) and should be very careful with this upgrade! We just landed the long waited PostgreSQL major version upgrade. Any site admins rebuilding Discourse from the command line will be upgraded to PostgreSQL 12 from the old PostgreSQL 10. We are running this new version for a while on Meta, and everything is working fine. PostgreSQL 12 brings lots of improvements that will be automatical…

I received the following message, so I assume the upgrade to PostreSQL 12 worked for me:

_Upgrade Complete_

_To complete the upgrade, rebuild again using:_

_./launcher rebuild app_

I am curious if this search bug will fix itself or if I need to do something.

---

_[View the full topic](https://meta.discourse.org/t/search-502-errors-in-2-5-0-beta6/154050)._