Summary

Only support Postgres. Remove MariaDB and MySQL support.

This is a SIGNIFICANT improvement with huge potential gain and some risks to mitigate.

This proposal is only our agreement on a single database; to proceed and remove code and documentation related specifically to MariaDB and MySQL. With this proposal we will make an effort but we are not committing to migration guides, scripts, tests, wizards, and case studies easing database migrations. The community is strongly encouraged to gather real-world data, to share and discuss this proposal with all users, encouraging them to create or sponsor creation of these critically important migration materials.

Status

Under discussion.

Who is Involved

• Unknown User (adamsaghy) (original proposal, PMC member)
• Unknown User (meonkeys) (FSIP author, PMC member)

Background/Motivation

• Speed up development, simplify maintenance
  
  • support one SQL flavor only
  • less edge/corner cases to manage
  • more reliable testing
  • faster CI build
• Leverage Postgres-specific features
  • sequences / identity columns for primary keys
  • native table partitioning
  • safer and more efficient transaction integrity support
  • more advanced indexing options
• Improve security

Goals and Exclusions

• Consolidate all relational database storage logic to work with Postgres only.
• Inform community and provide hints and tips for deployments needing to migrate to Postgres.
• Encourage entire community (especially all users: banks, vendors, and paid support orgs) to write or sponsor MariaDB/MySQL to Postgres migration guides, scripts, tests, wizards, case studies, etc.

Change Proposed

Remove code and documentation related specifically to MariaDB and MySQL.

Alternatives Considered

None.

Phases of work

1. DISCUSS
2. VOTE
3. TRACK
4. CLOSE