Skip to content

docs(database): add section on pg extensions setup #71

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

Open
evebrnd wants to merge 2 commits into
base: main
Choose a base branch
from
+12 −0
Open

docs(database): add section on pg extensions setup #71

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
da4a138
docs(db): add pg extensions setup section
evebrnd Jun 15, 2026
ee28ea6
Merge branch 'main' into docs/add-pg-extension-setup-section
evebrnd Jun 19, 2026
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
12 changes: 12 additions & 0 deletions docs/src/deployment/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,18 @@ spring:
validate-on-migrate: true
```

### PostgreSQL extensions

IDP-Core depends on PostgreSQL extensions that must be installed in the target database before running schema migrations that rely on them. You have three common options:

- Provision extensions directly via your Infrastructure as Code (for example Terraform resources) or checking them off in your cloud provider's database management dashboard
- Apply the provided initialization script (`/scripts/init-extensions.sql`) using `psql` from your deployment host
- Add a Flyway migration to your repository. Place a migration such as `V1__install_extensions.sql` in `db/migration` containing the `CREATE EXTENSION` statements. Flyway will execute the SQL file as part of the migration sequence.

@etiennej70 etiennej70 Jun 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can't have it like you did locally ? With "IF NOT EXISTS" it should not break anything in a flyway migration (and avoid this script outside the flyway pipeline) ?
Because it is hard to modify a migration when you install an opensource package / docker image ;)


Key note:

- Installing extensions requires superuser privileges or a role with `CREATE` extension privileges. If your application user lacks those privileges, perform installation as a DBA or during provisioning.

---

## Application Settings
Expand Down
Loading