PostgreSQL 19 Support - #69251
Draft
Dev-iL wants to merge 1 commit into
Draft
Conversation
Test PostgreSQL 19 during its beta cycle so CI surfaces compatibility issues before the GA release. Keep the beta tag in the matrix until the final pre-merge update swaps it to 19 and adds the user-facing support rows.
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
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.
Caution
Do not undraft/merge until PG19 reaches general availability!
Adds
19beta1toALLOWED_POSTGRES_VERSIONS/CURRENT_POSTGRES_VERSIONSindev/breeze/src/airflow_breeze/global_constants.pyso CI exercises PostgreSQL 19 during its beta cycle, surfacing any compatibility issues ahead of GA.dev/breeze/tests/test_selective_checks.pyand the breeze doc image/output snapshots are updated to match.This PR exists to validate CI compatibility with PostgreSQL 19 while it is still in beta. It intentionally targets the
19beta1image tag rather than a GA release, and per theTODOleft inglobal_constants.py,"14"should also be dropped once it reaches EOL (2026-11-13) and the default shifted.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Sonnet 5) following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.