Skip to content

Conversation

@ololobus
Copy link
Member

@ololobus ololobus force-pushed the alexk/config-neon-superuser-pg16 branch from 2f56f65 to 05ce512 Compare July 14, 2025 09:42
@ololobus ololobus merged commit b5184c4 into REL_16_STABLE_neon Jul 15, 2025
3 checks passed
@ololobus ololobus deleted the alexk/config-neon-superuser-pg16 branch July 15, 2025 15:20
github-merge-queue bot pushed a commit to neondatabase/neon that referenced this pull request Jul 15, 2025
## Problem

Currently `neon_superuser` is hardcoded in many places. It makes it
harder to reuse the same code in different envs.

## Summary of changes

Parametrize `neon_superuser` in `compute_ctl` via
`--privileged-role-name` and in `neon` extensions via
`neon.privileged_role_name`, so it's now possible to use different
'superuser' role names if needed. Everything still defaults to
`neon_superuser`, so no control plane code changes are needed and I
intentionally do not touch regression and migrations tests.

Postgres PRs:
- neondatabase/postgres#674
- neondatabase/postgres#675
- neondatabase/postgres#676
- neondatabase/postgres#677

Cloud PR:
- neondatabase/neon-archive-cloud#31138
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants