Configure Discourse to use a separate PostgreSQL server

maggiomj · 20 september 2023 om 14:29

No sir, no problem. Thanks for the info

dalu74 · 21 december 2023 om 16:04

In my case, it was because I had scram-sha-256 and not trust as the auth mechanism.
Because scram-sha-256 requires a physical user.
You can probably work around that by creating a user map in pg_ident.conf but I’m not sure how.

mpalmer · 22 december 2023 om 03:34

If by “physical user” you mean “Unix system user” then no, scram-sha-256 does not require such a user configured on the system. The peer method requires a system user, and trust is just a terrible idea all around when you’re using a remote database server.

harishg33 · 23 juli 2025 om 08:12

Will we have to include the following in addition to the existing process ?

CREATE EXTENSION vector;

since I see this extension in the discourse_docker postgres template ?

github.com/discourse/discourse_docker

templates/postgres.template.yml

c36fb7907


      
          
          - file:
              path: /usr/local/bin/create_db
              chmod: +x
              contents: |
                #!/bin/bash
                su postgres -c 'createdb $db_name' || true
                su postgres -c 'psql $db_name -c "create user $db_user;"' || true
                su postgres -c 'psql $db_name -c "grant all privileges on database $db_name to $db_user;"' || true
                su postgres -c 'psql $db_name -c "alter schema public owner to $db_user;"'
                su postgres -c 'psql template1 -c "create extension if not exists hstore;"'
                su postgres -c 'psql template1 -c "create extension if not exists pg_trgm;"'
                su postgres -c 'psql template1 -c "create extension if not exists vector;"'
                su postgres -c 'psql template1 -c "alter extension vector update;"' || true
                su postgres -c 'psql $db_name -c "create extension if not exists hstore;"'
                su postgres -c 'psql $db_name -c "create extension if not exists pg_trgm;"'
                su postgres -c 'psql $db_name -c "create extension if not exists vector;"'
                su postgres -c 'psql $db_name -c "alter extension vector update;"' || true
                sudo -u postgres psql $db_name <<< "update pg_database set encoding = pg_char_to_encoding('UTF8') where datname = '$db_name' AND encoding = pg_char_to_encoding('SQL_ASCII');" || true

Falco · 24 juli 2025 om 23:18

Dit wordt gebruikt door de Discourse AI core plugin, dus je hebt die nodig als je hem gebruikt.

harishg33 · 25 juli 2025 om 02:59

I don’t remember enabling that plugin. Infact I just checked that it is disabled. But recently when i rebuilt the image, when the latest commit went beyond this commit - GitHub - discourse/discourse at 0eab7daea450e1d7e416c46a23aaaf95687d4855, rake db:migrate started failing. When i used the commit just before the above one to bootstrap, it continued to work.

Now that I have enabled this extension, commits later than this is working without issues.

pfaffman · 25 juli 2025 om 05:54

Maar nu zit de ai-plugin in de kern, dus je hebt de extensie nodig, ongeacht of je de AI-plugin gebruikt (of deze expliciet probeert te verwijderen), toch?

Falco · 25 juli 2025 om 16:48

Oh dat is waar, aangezien migraties onafhankelijk van de ingeschakelde plugin worden uitgevoerd.

Topic		Antwoorden	Weergaven
External postgres setup not working Installation	4	693	11 april 2023
discourse容器部署方式下，如何在外部连接到数据库，例如使用DBeaver连接 Support	2	94	28 mei 2025
Error while doing discourse setup Installation	11	3018	6 oktober 2017
Using a PGSQL database outside of Docker? Installation	6	1494	12 oktober 2021
Accessing Database while discourse not running Dev	0	61	19 april 2025

Configure Discourse to use a separate PostgreSQL server

Gerelateerde topics