Add timeout to PostgreSQL readiness check in docker-entrypoint.sh

[Copilot]

The pg_isready check was waiting indefinitely for PostgreSQL without a timeout, causing containers to hang forever if the database never becomes available.

Changes:

• Add configurable timeout via POSTGRES_MAX_RETRIES (default: 60) and POSTGRES_RETRY_DELAY (default: 1s)
• Exit with clear error message after timeout, enabling orchestration systems to restart the container
• Calculate total timeout as POSTGRES_MAX_RETRIES * POSTGRES_RETRY_DELAY for accuracy with custom delays

Implementation:

# Wait for PostgreSQL with timeout
POSTGRES_MAX_RETRIES="${POSTGRES_MAX_RETRIES:-60}"
POSTGRES_RETRY_DELAY="${POSTGRES_RETRY_DELAY:-1}"
POSTGRES_RETRY_COUNT=0

POSTGRES_TIMEOUT=$((POSTGRES_MAX_RETRIES * POSTGRES_RETRY_DELAY))
echo "Waiting for Postgres... (max ${POSTGRES_MAX_RETRIES} attempts, ${POSTGRES_TIMEOUT}s timeout)"
while ! pg_isready -h "${POSTGRESQL_HOST:-postgres}" -p "${POSTGRESQL_PORT:-5432}" -U "${POSTGRESQL_USER:-postgres}" >/dev/null 2>&1; do
  POSTGRES_RETRY_COUNT=$((POSTGRES_RETRY_COUNT + 1))

  if [ "$POSTGRES_RETRY_COUNT" -gt "$POSTGRES_MAX_RETRIES" ]; then
    echo "ERROR: PostgreSQL did not become available after ${POSTGRES_MAX_RETRIES} attempts (${POSTGRES_TIMEOUT}s timeout)"
    exit 1
  fi

  sleep "$POSTGRES_RETRY_DELAY"
done

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.