Goal Summary:

Approve customer's own database using Postgres version 15  

TODO (Boaz)

1. Why do customers want their own DB

• Operational ease
• compliance requirements ?
• Features not supported by us (HA/DR)
• Performance not supported by us
• What data in PG is actually worth saving ?

2. What other experience do we have in RH on this topic

• involve OpenShift SME members who like to be involved  (re discussion on 3/3/2025  : rh-sa-plarsen rhn-support-milang rhn-support-rimartin
• Involve DanielMesser , they have similar use cases with Quay
• See Quay guidelines for HA ! We may be able to replicate their approach 1:1

3. None standard features:

• We do not support HA/DR. And should be clear about that
• Should we tell customers who want HA/DR "this capability is not supported by us, but we recommend you use your own" 
• Suggestions for approach for non standard features
  • It would be a consulting engagement
  • Involve one of our Postgres commercial partners (e.g. Crunchy) for support
  • Offer support for none standard use case (DR) only with support exception 

Goals and expected user outcomes:

1. Customers can confidently use this (required) version when they bring their own Postgres database
2. Red Hat can confidently support these customers

Acceptance Criteria:

1. Updated support statement is approved and published

Success Criteria or KPIs measured:

A list of specific, measurable criteria that will be used to determine if
the feature is successful. Include key performance indicators (KPIs) or
other metrics., etc. Initial completion during Refinement status.

<enter success criteria and/or KPIs here>