Skip to content

fix: add --username=postgres to initdb command to ensure postgres role exists#49

Merged
xar merged 1 commit intomainfrom
claude/issue-48-20250628_070331
Jun 28, 2025
Merged

fix: add --username=postgres to initdb command to ensure postgres role exists#49
xar merged 1 commit intomainfrom
claude/issue-48-20250628_070331

Conversation

@xar
Copy link
Copy Markdown
Owner

@xar xar commented Jun 28, 2025

This PR fixes the PostgreSQL instance creation issue where the "postgres" role didn't exist.

The initdb command was creating a superuser with the system username instead of 'postgres', causing connection failures. Adding --username=postgres explicitly creates the expected postgres superuser role during initialization.

Fixes #48

Generated with Claude Code

…e exists

The initdb command was creating a superuser with the system username instead 
of 'postgres', causing connection failures when the code tried to connect as 
the postgres user. Adding --username=postgres explicitly creates the expected
postgres superuser role during database cluster initialization.

Fixes #48

Co-authored-by: Samuel <xar@users.noreply.github.com>
@xar xar merged commit 814b23e into main Jun 28, 2025
2 checks passed
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.

Still cannot set password

1 participant