Database access issues after upgrade v3.5.2 -> v3.6.0.beta2

* [new branch] white_space_paragraph_parsing → origin/white_space_paragraph_parsing
t [tag update] beta → beta
t [tag update] latest-release → latest-release
* [new tag] v3.5.2 → v3.5.2
* [new tag] v3.6.0.beta2 → v3.6.0.beta2

This thread got me to this point:

I now have database access issues:
2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse LOG: provided user name (postgres) and authenticated user name (discourse) do not match
2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse FATAL: Peer authentication failed for user "postgres"
2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse DETAIL: Connection matched pg_hba.conf line 89: "local all postgres
peer"

List of databases
Name | Owner | Encoding | Locale Provider | Collate | Ctype | ICU Locale | ICU Rules | Access privileges
-------------+----------+----------+-----------------+-------------+-------------+------------+-----------+------------------------
b_discourse | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =Tc/postgres +
| | | | | | | | postgres=CTc/postgres +
| | | | | | | | discourse=CTc/postgres
c_discourse | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =Tc/postgres +
| | | | | | | | postgres=CTc/postgres +
| | | | | | | | discourse=CTc/postgres
discourse | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =Tc/postgres +
| | | | | | | | postgres=CTc/postgres +
| | | | | | | | discourse=CTc/postgres
postgres | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | |
template0 | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =c/postgres +
| | | | | | | | postgres=CTc/postgres
template1 | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =c/postgres +
| | | | | | | | postgres=CTc/postgres
(6 rows)
The multisite.yaml changed between these versions.
Original:
secondsite:
adapter: postgresql
database: b_discourse
pool: 25
timeout: 5000
db_id: 2
host_names:
- ``forum.domain.com

New:
mlp:
adapter: postgresql
database: discourse_mlp
username: discourse_mlp
password: applejack
host: dbhost
pool: 5
timeout: 5000
host_names:
- discourse.nudderdomain.com
- discourse.nudderdomain.internal

I never set any of the passwords or users for the multisite because it wasn’t required. I don’t know if discourse has some default for the others.

postgres=# SELECT * FROM pg_user;
usename | usesysid | usecreatedb | usesuper | userepl | usebypassrls | passwd | valuntil | useconfig
-----------+----------+-------------+----------+---------+--------------+----------+----------+-----------
postgres | 10 | t | t | t | t | ******** | |
discourse | 16385 | f | f | f | f | ******** | |

My initial problem migrated seemed to be a permissions issue from multisite. Database was down so I couldn’t check.

Will simply changing owner to discourse fix it? Do I need to add users and passwords for the multisite to make it match the current? Adding postres as the user to multisite.yml didn’t work for the migration.

What is the best LONG TERM FIX here.