Skip to content

Update main PostgreSQL images and synchronize patched Python dependencies - #267

Open
ibrahim halatci (ihalatci) wants to merge 4 commits into
masterfrom
ihalatci-pg-images-main-update
Open

ibrahim halatci (ihalatci) wants to merge 4 commits into
masterfrom
ihalatci-pg-images-main-update

Conversation

@ihalatci

@ihalatci ibrahim halatci (ihalatci) commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Changes

  • Update supported PostgreSQL pins: PG17 17.12, PG18 18.7, PG19 19.0 GA (image tags use 19.0). Preserve the existing support matrix and PG19 exclusion from Citus upgrade images.
  • Enable each per-major image's bookworm-pgdg main ${PG_MAJOR} APT components so libpq is available at the same exact package revision as the server. Preserve exact libpq/server/client/server-dev/dbgsym pins rather than selecting PG19 headers for older servers.
  • Regenerate all three base-image requirements files and stylechecker's dev-only requirements from citusdata/citus@223abeeb16eea4e881da5e9ba9877caee4f0ec51. No independent generated-requirements cherry-picks or automation ref changes.
Dependency Updated version
pyasn1 0.6.5
filelock 4.2.1
certifi 2026.10.19
Werkzeug 3.1.9
Black 26.10.1
Brotli 1.2.1
msgpack 1.2.3
tornado 6.6
urwid 4.0.7

Use compatible mitmproxy fork commit 0dac7e3f656baf0ac5b9bfcb1c13aa01cad2faa5 from the source lock. Preserve unrelated dependency versions and stylechecker tools version 0.8.33.

Dev publication and validation

  • GA image source: 48cf5f54798db98f0ecdcb84a21269136c4a1a9c; dev suffix -dev-48cf5f5.
  • Exact-commit build-test-images run: every dev job succeeded; both release publication jobs were skipped.
  • Independently retrieved all 13 exact-tag GHCR manifests: ghcr.io/citusdata/{extbuilder,exttester,failtester}:{17.12,18.7,19.0}-dev-48cf5f5 (9), citusupgradetester:{17.12,18.7}-dev-48cf5f5 (2), pgupgradetester:17.12-18.7-19.0-dev-48cf5f5, and stylechecker:0.8.33-dev-48cf5f5.
  • Isolated WSL Python 3.12 installation: all 58 base and 14 dev requirements were active and installed at exact exported versions, with zero marker skips; dependency check and mitmdump --version passed.
  • Actual image build logs confirm patched base packages and Black 26.10.1 in the Alpine stylechecker (Python 3.14.10). Previous matched-pin build confirms PG17 libpq 17.12 rather than PG19.

Paired Citus gate

GA dev-image testing: paired PR citusdata/citus#8973 is at head 36a1c1a5b5792f48a1179c58aa5f6b9c63b31ca2, consuming the GA image source and -dev-48cf5f5 suffix above. Its GA-head Build & Test run finished FAILURE: 134 jobs passed, two failed (PG19 isolation and downstream CI aggregate), two benchmarks skipped. The sole test diff is a 360-second timeout/cancellation in isolation_create_distributed_table_concurrently. An unchanged local PG19.0 replay passed; an intermittent timeout is suspected, not established as harmless or pre-existing. Packaging and CodeQL passed, but the consumer full GA gate remains red. No rerun or additional push has been performed. Dependency SSOT provenance remains 223abeeb16eea4e881da5e9ba9877caee4f0ec51.

Historical RC2 evidence: corrected-head Build & Test run 43424196914 on 9b24f89d7ecd189a84b5c93604e02fa9ab427d50 succeeded with 136 jobs passed and two benchmarks skipped. Twelve exact saved-fixture/version replays and 18 direct role/node/version assertions also passed across PG17.12/PG18.7/PG19rc2. These results do not establish GA-head CI success.

Resolved hold history

The shared planner port introduced a deterministic wrong-result regression, first reported on release14 PG18.7 and subsequently reproduced on main across all three supported PostgreSQL versions. This was not a blanket pre-existing issue. The earlier 136-pass run 43415812122 on 99fab5d1803c0186ce127f200ac8489de0bc7aa8 missed these cases and did not clear the hold. Main correction 29adb0b6361bf6b10d1d2883ddeaf51ca01056b4 requires matching transformed-relation evidence before original nullable-relation conversion; previous corrected head 9b24f89d7ecd189a84b5c93604e02fa9ab427d50 corrected regression fixture placement for regular-user/random-MX execution. The exact fixture replays, role/node assertions, and final full CI above now resolve the hold. At the time, no image-source change or rebuild was required.

This remains the dev-image testing/review phase. No merges or stable image promotion are authorized. Existing Dependabot PRs and automation pairs remain open; the paired image/Citus PRs and citusdata/mitmproxy#6 remain open.

Allow APT to resolve libpq independently of the server version because PGDG does not publish matching libpq packages for PostgreSQL 17.12.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Enable each image's PostgreSQL major APT component and restore exact libpq pins to avoid using PG19 client headers with older servers.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Regenerate base and dev-only requirements from citusdata/citus commit 223abeeb16eea4e881da5e9ba9877caee4f0ec51, including the compatible mitmproxy fork and patched dependency versions.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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