7. Future Considerations
7. Future Considerations
← 6. Rationale | Index | Next: Appendix A. Glossary →
7.1 Future Considerations
The following considerations apply to the evolution of the containerized PostgreSQL stack after the PostgreSQL 18 baseline is established:
| Consideration | Recommendation | Rationale |
|---|---|---|
| Extension version pinning | SHOULD | Extension versions SHOULD be documented explicitly to avoid silent drift across environments |
| Debezium connector revalidation | SHOULD | Debezium PostgreSQL connector compatibility SHOULD be revalidated for each PostgreSQL 18 point release |
| RFC evolution | MAY | The database architecture MAY evolve into separate Architecture and Specification RFCs if upgrade mechanics and configuration contracts expand |
| Re-introduction of extensions | MAY | If Apache AGE, pgvector, or pg_net are required in the future, they MAY be re-added to the container image with corresponding Prisma migration updates; re-introduction requires a new RFC or amendment |
Document Navigation
| Previous | Index | Next |
|---|---|---|
| ← 6. Rationale | Table of Contents | Appendix A. Glossary → |
End of Section 7