Skip to content
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.

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

postgres: always create socketDir during init if not already present #88

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

shivaraj-bh
Copy link
Member

If the socketDir is in tmpfs, or if it is deleted by some other process, we would want the socketDir to be created, if not already present, on restarts.

If the socketDir is in tmpfs, or if it is deleted by some other process, we would want the socketDir to be created, if
not already present, on restarts.
@shivaraj-bh shivaraj-bh merged commit 9b806b5 into main Jan 31, 2024
3 checks passed
@shivaraj-bh shivaraj-bh deleted the create-socketdir branch January 31, 2024 13:17
shivaraj-bh added a commit to nammayatri/nammayatri that referenced this pull request Jan 31, 2024
postgres-init process will now create socketDir if it is not already present.
This is important for `replica` process because it doesn't create the datadir,
it is created by `pg-basebackup` process.

This was fixed in services-flake, here:
juspay/services-flake#88
hkmangla pushed a commit to nammayatri/nammayatri that referenced this pull request Jan 31, 2024
postgres-init process will now create socketDir if it is not already present.
This is important for `replica` process because it doesn't create the datadir,
it is created by `pg-basebackup` process.

This was fixed in services-flake, here:
juspay/services-flake#88
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.

1 participant