Add \c mattermost step to PostgreSQL preparation grants

[ewwollesen]

Summary

In the PostgreSQL preparation steps for v15.x or later (database-preparation step 5e), the ALTER SCHEMA public and GRANT USAGE, CREATE ON SCHEMA public commands operate on the current database's public schema. Without first connecting to the mattermost database, those grants are applied to whatever database the admin happens to be connected to (typically postgres), leaving the actual mattermost database without the required schema permissions.

This PR adds a \c mattermost step between ALTER DATABASE and the schema-level commands so the grants land on the right schema.

Before:

ALTER DATABASE mattermost OWNER TO mmuser;
ALTER SCHEMA public OWNER TO mmuser;
GRANT USAGE, CREATE ON SCHEMA public TO mmuser;

After:

ALTER DATABASE mattermost OWNER TO mmuser;
\c mattermost
ALTER SCHEMA public OWNER TO mmuser;
GRANT USAGE, CREATE ON SCHEMA public TO mmuser;

Test plan

• Verify the rendered page at deployment-guide/server/preparations.html#database-preparation shows the new \c mattermost line in the step 5e code block.
• Confirm running the updated sequence in psql against a fresh PostgreSQL 15+ instance results in mmuser owning the public schema of the mattermost database.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@ewwollesen has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 30 minutes and 8 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1c2fbf6e-b5d2-4b89-98cd-7e33647e6680

📥 Commits

Reviewing files that changed from the base of the PR and between 1fdd8d1 and b75ae92.

📒 Files selected for processing (1)

• source/deployment-guide/server/preparations.rst

📝 Walkthrough

Walkthrough

Documentation update to PostgreSQL v15.x+ database preparation instructions adds an explicit connection command (\c mattermost) after setting database ownership, ensuring subsequent schema and grant operations execute in the correct database context.

Changes

Cohort / File(s)	Summary
PostgreSQL Setup Documentation source/deployment-guide/server/preparations.rst	Added \c mattermost command to ensure ALTER SCHEMA and related operations execute within the mattermost database context.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a database connection step to PostgreSQL preparation instructions.
Description check	✅ Passed	The description provides comprehensive context explaining the problem, the solution, and test steps; it is directly related to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-postgres-prep-connect-step

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Updates the Mattermost Server deployment preparation docs to ensure PostgreSQL schema grants are applied to the correct database when using PostgreSQL v15.x+.

Changes:

• Adds an explicit \c mattermost step before running schema-level ALTER SCHEMA / GRANT commands in the PostgreSQL v15.x+ preparation flow.

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 1fdd8d1

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA d209c34

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA f4e6162

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA b75ae92

[ewwollesen]

@hanzei I am 99% sure that connect step is needed prior to changing those permissions. I'm also pretty certain this is why we have so many search_path and current_schema issues with the Postgres migration.

[hanzei]

Good catch