fix(quickstart): wait for final TimescaleDB process#4
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #3
Problem
TimescaleDB starts a temporary PostgreSQL process during first-run tuning. The existing
pg_isreadyhealthcheck could mark that temporary process healthy, allowing migrations to race the subsequent restart.Changes
timescale/timescaledb:2.28.2-pg15postgresprocess before reporting healthyVerification
docker compose -f docker-compose.quickstart.yml config --quietpnpm script:auditpnpm boundary:auditgit diff --checkA clean-volume boot on the isolated test VM will run after CI and merge.