the-custodian/docs/changes/netkingdom-target-2026-10-18/forgejo-postgres-source-r1/runtime-setup-refinements.json
codex 83078392c0
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Reject generated-only commits / generated-commit-guard (push) Successful in 8s
Verify PostgreSQL source recovery and preserve tracing context across hooks
2026-10-18 03:29:54 +02:00

24 lines
1.2 KiB
JSON

{
"original_attempts_preserved": [
"database-runtime.json",
"database-initial-failure.json",
"database-initial-failure.log",
"database-cleanup.json",
"database-runtime-attempt2.json",
"database-attempt2-failure.json",
"database-attempt2-failure.log",
"database-cleanup-attempt2.json"
],
"observed_cause": "Image initialization intentionally clears PGHOST and PGHOSTADDR for its own SQL; a custom-only socket prevents creation of the requested synthetic database. pg_isready can accept during that temporary initialization server.",
"public_entrypoint_sha256": "sha256:9c440299ae04a0a79d55b8bf03307036d890a40979d2fb698073c9050d4b20a5",
"public_entrypoint_source": "/usr/local/bin/docker-entrypoint.sh in the pinned public database image",
"source_line": 212,
"refinements": [
"Require final postgres PID 1 and an actual version query in the exact database",
"Preserve the default in-container socket alongside the one exported synthetic socket",
"Use fresh independently identified containers and volumes for failed initialization refinements, after exact owned cleanup"
],
"application_package_tests_in_failed_setup_attempts": 0,
"production_changes": false,
"real_credentials": false
}