I’m unsure how to confirm the DB migrate has run successfully.
Thanks in advance for any help.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 18, 2019, 11:51pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/2 "2019-03-18T23:51:42Z")
> [@DeanMarkTaylor](#):
>
> I am running a multi-site install.
Do you have code to run migrations on all sites in your app.yml ?
---
### Author:  [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [March 18, 2019, 11:57pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/3 "2019-03-18T23:57:50Z")
I’m pretty sure I do - as it’s worked since ~ ~~April~~ May 2017.
The last time I had this kind of issue I worked around it, seen here:
[https://meta.discourse.org/t/multisite-builds-are-currently-broken-under-new-native-theme-changes/60865](https://meta.discourse.org/t/multisite-builds-are-currently-broken-under-new-native-theme-changes/60865)
And then undid my change after Sam’s fix.
I’ll test these changes again.
---
### Author:  [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [March 19, 2019, 12:12am UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/4 "2019-03-19T00:12:58Z")
Thanks @Falco for reminding be of the migrations the yml config - this pointed me in the right direction.
I can confirm that the following change “fixed” this issue for me:
[https://meta.discourse.org/t/multisite-builds-are-currently-broken-under-new-native-theme-changes/60865/10?u=deanmarktaylor](https://meta.discourse.org/t/multisite-builds-are-currently-broken-under-new-native-theme-changes/60865/10)
However previously Sam made a change because of this happening twice:
[https://meta.discourse.org/t/multisite-builds-are-currently-broken-under-new-native-theme-changes/60865/13?u=deanmarktaylor](https://meta.discourse.org/t/multisite-builds-are-currently-broken-under-new-native-theme-changes/60865/13)
This might need visiting again.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 19, 2019, 12:15am UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/5 "2019-03-19T00:15:53Z")
@sam changes where addressing the specific cases that you reported, but the way it’s setup it will always blow when a migrations adds a column.
@riking adresses that on the last post there:
[https://meta.discourse.org/t/multisite-builds-are-currently-broken-under-new-native-theme-changes/60865/15?u=falco](https://meta.discourse.org/t/multisite-builds-are-currently-broken-under-new-native-theme-changes/60865/15)
Not sure if his suggestion is the more appropriate one, or if we should add another hook for a multisite template to use.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 19, 2019, 12:20am UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/6 "2019-03-19T00:20:37Z")
Are you saying that your multisite instances get migrated a different way and that a multisite upgrade will fail right now?
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 19, 2019, 12:23am UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/7 "2019-03-19T00:23:15Z")
Using `rake db:migrate` runs the migrations for the default site. For multisite you need to use `rake multisite:migrate`.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 19, 2019, 12:27am UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/8 "2019-03-19T00:27:57Z")
Got it. But I thought that I always see a bootstrap do a multisite migrate, right?
---
### Author:  [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [March 19, 2019, 12:30am UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/9 "2019-03-19T00:30:58Z")
My understanding is that this depends on your specific multisite configuration.
Certainly the “recommended” way back in 2017 was to include this:
```plaintext
after_bundle_exec:
- exec: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate
```
Which when I ran a rebuild it failed to build the multisite a bit earlier today.
Noting when the CSS is compiled early for theme updates etc before the DB migration…
… because of this it makes use of SQL queries that can’t complete.
Hence moving an execution of `bundle exec rake db:migrate` before `bundle exec rake multisite:migrate` in the `before_bundle_exec` section works around this.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 19, 2019, 8:44am UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/10 "2019-03-19T08:44:06Z")
Basically in a multisite you have to run `bundle exec rake multisite:migrate` prior to `precompile`, in this case you clearly did not.
The problem is that we were m missing some hooks here which make this a nightmare to fix cleanly.
I added some per:
[https://github.com/discourse/discourse\_docker/commit/5716d28f3c6d2a20a9fe2491fce6c131c9951f5c](https://github.com/discourse/discourse_docker/commit/5716d28f3c6d2a20a9fe2491fce6c131c9951f5c)
I you use:
```plaintext
after_db_migrate:
- exec: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate
```
You should be all good.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 19, 2019, 1:23pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/11 "2019-03-19T13:23:36Z")
Well, now I’m really confused.
I don’t have that `after_db_migrate` stanza and have had this multisite instance running for well over a year. I thought that the web template was doing the multisite migrate and haven’t noticed any problems.
Should I add that `after_db_migrate` stanza?
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [March 19, 2019, 1:38pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/12 "2019-03-19T13:38:31Z")
> [@pfaffman](#):
>
> I thought that the web template was doing the multisite migrate
No, there’s no reference to multisite:migrate in the whole discourse\_docker repository.
I guess you must have `bundle exec rake multisite:migrate` somewhere in your config file? It’s probably run towards the end, which can potentially cause the issues described in this topic.
The new `after_db_migrate` hook Sam added means you can run `multisite:migrate` right next to the regular `db:migrate`, which is the best place for it.
I guess the best thing would be for us to add a “multisite” template to discourse\_docker, which people can add to their templates (including on our own infrastructure). What do you think @sam?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 19, 2019, 1:53pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/13 "2019-03-19T13:53:59Z")
I swear that I see “multisite” in every rebuild (ooooh, perhaps that’s just a test for multisite). And I don’t see a reference to it in my yml file.
I’m very confused how either these databases have been getting migrated or how they are working if they haven’t. And how your multisite databases get migrated.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [March 19, 2019, 1:59pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/14 "2019-03-19T13:59:11Z")
Adding the multisite:migrate line is part of the #howto for multisite setups
> [@Multisite configuration with Docker](https://meta.discourse.org/t/multisite-configuration-with-docker/14084):
>
> warning While multisite is supported in the Discourse application, this is an advanced sysadmin setup. If you don’t know what you’re doing, do not set up multisite. The Discourse team is unable to provide multisite configuration support. If you wish to host multiple domains on a singled Docker setup, you’ll need a multisite configuration. Here are the basic building blocks for one. Understand hooks Multisite is a fairly advanced topic. Before attempting a multisite build, spend some time…
> [@pfaffman](#):
>
> how your multisite databases get migrated
Using the multisite:migrate command as described in the #howto 😉
> [@pfaffman](#):
>
> I’m very confused how either these databases have been getting migrated
This is certainly surprising. I think you would be noticing issues if you hadn’t migrated for a whole year. If it was only a few weeks, then it might be possible to continue running on an old schema without too many errors. Have you modified one of the other templates to include multisite:migrate?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 19, 2019, 2:05pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/15 "2019-03-19T14:05:18Z")
I just looked again and don’t see anything like that in the yml. I’m sure I didn’t modify any templates. I’ll have a closer look in a few days and see what happens when I do a bootstrap.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 20, 2019, 4:24am UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/16 "2019-03-20T04:24:37Z")
> [@david](#):
>
> I guess the best thing would be for us to add a “multisite” template to discourse\_docker, which people can add to their templates (including on our own infrastructure). What do you think @sam?
Maybe… if you feel strongly about it you can add a trivial `web.multisite.yml` so people can mix that in which is less confusing than typing the hook.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [March 21, 2019, 9:20pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/17 "2019-03-21T21:20:07Z")
The point of the linked post of mine above was that I was fairly sure that changing the _default_ action – the content of what’s now `hook: db_migrate` – from db:migrate to multisite:migrate (i.e. a 1-line PR) was safe, but with a “I cannot verify this statement” disclaimer.
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [March 22, 2019, 8:37pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/18 "2019-03-22T20:37:48Z")
> [@riking](#):
>
> from db:migrate to multisite:migrate
Is there EVER a case where we want to `db:migrate` but not `multisite:migrate`? 🤔
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 25, 2019, 3:51pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/19 "2019-03-25T15:51:45Z")
EDIT: Well, I think that what happened was that my `multi.yml` got truncated somehow. And the one that I’d been using had been doing migrations as expected, but I’d forgotten, and when I grepped the file, I didn’t see the migration.
Thankfully the backup that I had contained the whole file. I modified it to use the new hook and all is well.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 25, 2019, 8:23pm UTC](https://meta.discourse.org/t/activerecord-pg-error-column-categories-search-priority-does-not-exist/111982/23 "2019-03-25T20:23:51Z")