Skip to content

fix: initdb shouldn't CREATE EXTENSION beyond_auth #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jaredLunde merged 1 commit into from
Jun 21, 2026
Merged

fix: initdb shouldn't CREATE EXTENSION beyond_auth #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docker/initdb.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,12 @@
# - public : the app's own migrations
set -euo pipefail

# beyond_auth owns (creates) the `auth` schema, so let the extension make it
# rather than pre-creating it (pre-creating triggers "schema auth is not a member
# of extension"). The auth server's CREATE EXTENSION IF NOT EXISTS is then a no-op.
# Create the schemas the primitives expect. The auth server manages the
# beyond_auth extension itself in its own migrations (the extension is installed
# in the image), so initdb must NOT create it here — doing so makes the auth
# server's migration fail with "function authz_check already exists".
psql -v ON_ERROR_STOP=1 --username "$POSTGRES_USER" --dbname "$POSTGRES_DB" <<'SQL'
CREATE EXTENSION IF NOT EXISTS beyond_auth;
CREATE SCHEMA IF NOT EXISTS auth;
CREATE SCHEMA IF NOT EXISTS queue;
SQL

Expand Down