We have followed below blog to setup Discourse to use separate postgres(AWS RDS). [image] Configure Discourse to use a separate PostgreSQL server Self-Hosting Let’s say you’re using AWS RDS, or an existing PostgreSQL server managed elsewhere. It’s fairly straightforward to get Discourse to use such a setup, without needing to grant superuser privileges to anything that Discourse itself runs. Here’s how. Prerequisites Discourse requires PostgreSQL’s major version to match what we ship with in our docker images; if you try to run on a newer or older version, it might work, but we don’t guarantee it, and if something breaks in the future, you get to … Getting below error(image attached) after running ./launcher rebuild app: Caused by: PG::InvalidSchemaName: ERROR: no schema has been selected to create in LINE 1: CREATE TABLE "schema_migrations" ("version" character varyin... ^ /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:110:in `exec' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rack-mini-profiler-3.0.0/lib/patches/db/pg.rb:110:in `async_exec' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:48:in `block (2 levels) in execute' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.4.3/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.4.3/lib/active_support/dependencies/interlock.rb:41:in `permit_concurrent_loads' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:47:in `block in execute' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.4.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.4.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.4.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.4.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/connection_adapters/abstract_adapter.rb:765:in `block in log' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.4.3/lib/active_support/notifications/instrumenter.rb:24:in `instrument' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/connection_adapters/abstract_adapter.rb:756:in `log' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:46:in `execute' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/connection_adapters/abstract/schema_statements.rb:325:in `create_table' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/schema_migration.rb:23:in `create_table' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/migration.rb:1259:in `initialize' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/migration.rb:1117:in `new' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/migration.rb:1117:in `up' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/migration.rb:1092:in `migrate' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.4.3/lib/active_record/tasks/database_tasks.rb:262:in `migrate' /var/www/discourse/lib/tasks/db.rake:246:in `block (2 levels) in ' /var/www/discourse/lib/distributed_mutex.rb:53:in `block in synchroniz [image]

Without looking too closely, I think that might mean that you created the database server, but didn’t create the discourse database? Or didn’t provide the database name in the settings?

DB setting in app.yml are as below: env: DISCOURSE_DB_USERNAME: discourse DISCOURSE_DB_PASSWORD: “XXX” DISCOURSE_DB_HOST: xxx.rds.amazonaws.com DISCOURSE_DB_NAME: discourse I am able to connect with this DB using pgAdmin. I have executed below commands in this DB for discourse: CREATE USER discourse PASSWORD ‘XXX’; CREATE DATABASE discourse OWNER discourse; CREATE EXTENSION hstore; CREATE EXTENSION pg_trgm;

Hello @deepak_b :slight_smile: You marked this post as the solution. Did you resolve your issue? If you do, can you share how you did? this way it could help other people in the future.

External postgres setup not working

Product Support Self-hosting

deepak_b March 30, 2023, 4:28am 4

Please help on this issue.

Topic		Replies	Views
Configure Discourse to use a separate PostgreSQL server Self-Hosting how-to	53	31794	October 21, 2026
Error while doing discourse setup Self-hosting	11	3358	October 6, 2017
Use a postgres schema Self-hosting	0	551	July 13, 2020
I want to keep PostgreSQL database on separate server [standard docker install] Self-hosting	4	937	August 9, 2022
Docker/Postgre problem, need help Marketplace delivered	3	1082	August 14, 2020

External postgres setup not working

Related topics