Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

We'll need to support Postgres 17, as of 1.37.0, backstage has bumped their supported versions to 13 - 17 (testing the newest and oldest in the range).

Support policy docs (1) (2) and other related collateral will need to be updated.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

• Users can deploy RHDH with PostgreSQL 17 as their backing external database with confidence that it is covered in our testing.
• Customers planning upgrades to PostgreSQL 17 know that it is officially supported under our policy.
• Align RHDH database support with upstream Backstage to ensure consistency and reduce friction for customers. Also because it is mentioned as supported by Backstage, and plugins might depend on it

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

• PostgreSQL 17 is included in the RHDH test matrix.
• All existing test suites pass using PostgreSQL 17 as the external database.
• No regressions in reliability, performance, or scalability are observed.
• Documentation and support policy pages are updated to list PostgreSQL 17 as a supported version.

Out of Scope (Optional)

High-level list of items that are out of scope.

• No change to the default DB version deployed by the Operator or Helm Chart in the local DB use case, which is unsupported
• No changes to features or functionality specific to PostgreSQL beyond ensuring compatibility.

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

• Customers upgrading to PostgreSQL 17 can expect the same level of support as with other covered versions.

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

• Update RHDH support policy documentation to explicitly include PostgreSQL 17.
• Ensure installation guides and compatibility matrices are updated to list PostgreSQL 17.
• Mention this support in the Release Notes
• [To be confirmed] Drop support for PostgreSQL 14?