fix: PostgreSQL authentication issue during instance creation #45
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes authentication issue where temporary PostgreSQL instance creation failed due to password prompts on TCP/IP connections. Changes: - Modified waitForPostgreSQLReady() to use Unix socket directory parameter - Updated all psql commands to use Unix socket (-h socketDirectory) instead of TCP/IP (-h 127.0.0.1) during temporary startup - This uses peer authentication (no password) instead of md5 (password required) The issue occurred because initdb sets --auth-host=md5 for TCP/IP connections but the postgres user doesn't have a password set during temporary startup. Unix socket connections use peer authentication which doesn't require passwords. Fixes #43 Co-authored-by: Samuel <xar@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes authentication issue where PostgreSQL instance creation failed due to password prompts on TCP/IP connections.
The problem occurred during temporary PostgreSQL startup for database creation, where the code was using TCP/IP connections (
-h 127.0.0.1) which require md5 authentication, but the postgres user doesn't have a password set during this phase.The fix switches to Unix socket connections which use peer authentication and don't require passwords.
Fixes #43
🤖 Generated with Claude Code